(original) (raw)
Hi Christian,
+ Justin who works on PGO.
Cheers,
-Quentin
On Jun 24, 2015, at 6:05 PM, Christian Convey <christian.convey@gmail.com> wrote:Hi all,\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_Does anyone know of a good solution to the following? I'm trying to find a good way to stably associate distinct ID numbers with different BB in a module. As long as the module's IR hasn't changed in any way whatsoever, I'd like to be guaranteed to always generate the same ID <--> BB mapping. Or if the mapping is ambiguous, because two or more mappings between BB's and ID's are indistinguishable (isomorphic?), I'd like to be sure I at least can reliably re-obtain some mapping in that equivalence class.This seems related to a debate / bug-report regarding the arbitrary nature of (pseudo?) labels in LLVM assembly. E.g.,"; label:3".It also looks like llvm-diff does something similar to what I want in its FunctionDifferenceEngine class. But I think llvm-diff allows for the two IR's to differ, and uses approximate matching. I don't need any graceful degradation when the IR has changed, but I need exact matching when the IR hasn't changed.In the worst-case scenario, I could make a sweep through all of the module's BB's and just tag each BB with a distinct serial number in its metadata. But I'd like to avoid this if possible, partly because I'd like there to be a chance of the BB <--> ID mapping remaining valid if I run Clang.Thanks, Christian
LLVM Developers mailing list
LLVMdev@cs.uiuc.edu http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev