http://llvm.org/bugs/show_bug.cgi?id=18748
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: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected],
[email protected], [email protected]
Classification: Unclassified
Given
------------------------------
.section __TEXT,__cstring
L1:
.section __TEXT,__ustring
L2:
------------------------------
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.
_______________________________________________
LLVMbugs mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
