Displaying 3 results from an estimated 3 matches for "af3e3f76".
2012 Mar 30
2
[LLVMdev] Mangling of UTF-8 characters in symbol names
Why is it that high (>127) bytes in symbol names get mangled by LLVM into
_XX_, where XX is the hex representation of the character? Is this required
by ELF or some similar standard? This behavior is inconsistent with GCC.
Sean
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2012 Mar 30
0
[LLVMdev] Mangling of UTF-8 characters in symbol names
On Fri, Mar 30, 2012 at 12:12 PM, Sean Hunt <scshunt at csclub.uwaterloo.ca> wrote:
> Why is it that high (>127) bytes in symbol names get mangled by LLVM into
> _XX_, where XX is the hex representation of the character? Is this required
> by ELF or some similar standard? This behavior is inconsistent with GCC.
I think it's just so that we have a way to actually write out
2012 Mar 31
2
[LLVMdev] Mangling of UTF-8 characters in symbol names
...;
scshunt at natural-flavours:~$ nm test.o
00000004 C iλ
scshunt at natural-flavours:~$
As you can see, the nm output includes the literal lambda.
Sean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120330/af3e3f76/attachment.html>