Displaying 3 results from an estimated 3 matches for "__unnamed_1_1".
Did you mean:
__unnamed_1_0
2008 Nov 23
2
[LLVMdev] RFC: Mangling Unnamed Global Values
...#39;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
00000000000244b0 (__DATA,__cfstring) non-external __unnamed_1_1
...
I think that prepending the PrivateGlobalPrefix to these names would
be the way to go. My question is whether getValueName() should do the
prepending or should the individual back-end do it? I think that
getValueName() should do it so that it's consistent, but then the
prefix needs...
2008 Nov 24
0
[LLVMdev] RFC: Mangling Unnamed Global Values
...his 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
> 00000000000244b0 (__DATA,__cfstring) non-external __unnamed_1_1
> ...
>
> I think that prepending the PrivateGlobalPrefix to these names would
> be the way to go. My question is whether getValueName() should do the
> prepending or should the individual back-end do it? I think that
> getValueName() should do it so that it's consistent, but...
2008 Nov 24
2
[LLVMdev] RFC: Mangling Unnamed Global Values
...ective-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
>> 00000000000244b0 (__DATA,__cfstring) non-external __unnamed_1_1
>> ...
>>
>> I think that prepending the PrivateGlobalPrefix to these names would
>> be the way to go. My question is whether getValueName() should do the
>> prepending or should the individual back-end do it? I think that
>> getValueName() should do it so that i...