Displaying 3 results from an estimated 3 matches for "__unnamed_1_37".
Did you mean:
__unnamed_1_0
2008 Nov 23
2
[LLVMdev] RFC: Mangling Unnamed Global Values
Hi all,
Right now the Mangler::getValueName() method will produce something
like "__unnamed_1_37" for a global value that doesn't have a name.
This is wrong for Objective-C where CFStrings will get these labels,
thus preventing the linker from coalescing them.
[/tmp]> nm -s __DATA __cfstring -m foo.o
00000000000244d0 (__DATA,__cfstring) non-external __unnamed_1_0
0000000000024...
2008 Nov 24
0
[LLVMdev] RFC: Mangling Unnamed Global Values
Can symbols with external linkage but no name be converted
to have internal linkage? Would that solve the problem?
Dan
On Nov 23, 2008, at 2:15 AM, Bill Wendling wrote:
> Hi all,
>
> Right now the Mangler::getValueName() method will produce something
> like "__unnamed_1_37" for a global value that doesn't have a name.
> This is wrong for Objective-C where CFStrings will get these labels,
> thus preventing the linker from coalescing them.
>
> [/tmp]> nm -s __DATA __cfstring -m foo.o
> 00000000000244d0 (__DATA,__cfstring) non-external __unnam...
2008 Nov 24
2
[LLVMdev] RFC: Mangling Unnamed Global Values
...al linkage but no name be converted
> to have internal linkage? Would that solve the problem?
>
> Dan
>
> On Nov 23, 2008, at 2:15 AM, Bill Wendling wrote:
>
>> Hi all,
>>
>> Right now the Mangler::getValueName() method will produce something
>> like "__unnamed_1_37" for a global value that doesn't have a name.
>> This is wrong for Objective-C where CFStrings will get these labels,
>> thus preventing the linker from coalescing them.
>>
>> [/tmp]> nm -s __DATA __cfstring -m foo.o
>> 00000000000244d0 (__DATA,__cfstring)...