[LLVMbugs] [Bug 18748] New: Inconsistent handling of __TEXT, __cstring and __TEXT, __ustring with regards to L labels

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Wed Feb 5 16:23:14 PST 2014


            Bug ID: 18748
           Summary: Inconsistent handling of  __TEXT,__cstring and
                    __TEXT,__ustring with regards to L labels
           Product: libraries
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: MC
          Assignee: unassignedbugs at nondot.org
          Reporter: rafael.espindola at gmail.com
                CC: grosbach at apple.com, kledzik at apple.com,
                    lhames at gmail.com, llvmbugs at cs.uiuc.edu
    Classification: Unclassified


.section  __TEXT,__cstring

.section  __TEXT,__ustring

We put L1 in symbol table but not L2. Whatever relocation issues that exist
that require L1 to be visible also exist for L2, no?

If the relocation issue still exists, it looks like we would be miscompiling
utf-16 string.

The bigger question is why put L symbols in the symbol table? If the are
needed, why not just have codegen use "l"?

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20140206/01e605b4/attachment.html>

More information about the llvm-bugs mailing list