search for: _zl3byepi1

Displaying 2 results from an estimated 2 matches for "_zl3byepi1".

Did you mean: _zl3byepi
2015 Apr 14
5
[LLVMdev] [cfe-dev] A problem with names that can not be demangled.
...t; $ clang++ -c -emit-llvm t1.cpp -o t2.bc > > $ llvm-link t1.bc t2.bc -o t23.bc > > $ clang -c t23.bc > > $ nm t23.o > > > > t1.o and t2.o have the same named function “_ZL3ByePi”. In order to > distinguish them, > > one gets a ‘1’ appended to it, making it “_ZL3ByePi1”. > > > > While the code is all correct, the problem is that this modified name > cannot be demangled. > > > > That is what I am trying to fix. > > > > In similar situations gcc appends a ‘.’ before appending the > discriminating number, making “_ZL3ByePi.1...
2015 Apr 14
0
[LLVMdev] [cfe-dev] A problem with names that can not be demangled.
...----- cmd sequence ------- $ clang++ -c -emit-llvm t1.cpp -o t1.bc $ clang++ -c -emit-llvm t1.cpp -o t2.bc $ llvm-link t1.bc t2.bc -o t23.bc $ clang -c t23.bc $ nm t23.o t1.o and t2.o have the same named function “_ZL3ByePi”. In order to distinguish them, one gets a ‘1’ appended to it, making it “_ZL3ByePi1”. While the code is all correct, the problem is that this modified name cannot be demangled. That is what I am trying to fix. In similar situations gcc appends a ‘.’ before appending the discriminating number, making “_ZL3ByePi.1” The following change in lib/IR/ValueSymbolTable.cpp seems to fix...