Displaying 3 results from an estimated 3 matches for "_tst1".
Did you mean:
tst1
2010 May 07
3
[LLVMdev] AsmPrinter behavior
I compile these two lines in llc
@tst1 = internal global [4 x i8] zeroinitializer;
@tst2 = internal global [4 x i8] [i8 0, i8 1, i8 2, i8 3];
@tst1 is emited via MCStreamer::EmitCommonSymbol
while the other is emited via MCStreamer::EmitLabel followed by
MCStreamer::EmitBytes
from what I can tell, only symbols with common linkage should me emitted
by MCStreamer::EmitCommonSymbol,
is this the
2010 May 07
1
[LLVMdev] AsmPrinter behavior
...es
> >
> > from what I can tell, only symbols with common linkage should me emitted by MCStreamer::EmitCommonSymbol,
> >
> > is this the expected behavior or should I fix it?
>
> This is expected behavior. tst1 should be emitted with something like:
>
> .local _tst1
> .comm _tst1, ...
>
> based on the exact syntax of your target. If your target supports .lcomm, you can also enable that.
>
> -Chris
>
> This seems counter intuitive to me, I can understand that C assigned that behavior somewhat arbitrarily to uninitialized global variable...
2010 May 07
0
[LLVMdev] AsmPrinter behavior
...t I can tell, only symbols with common linkage should me emitted
>> by MCStreamer::EmitCommonSymbol,
>> >
>> > is this the expected behavior or should I fix it?
>>
>> This is expected behavior. tst1 should be emitted with something like:
>>
>> .local _tst1
>> .comm _tst1, ...
>>
>> based on the exact syntax of your target. If your target supports .lcomm,
>> you can also enable that.
>>
>> -Chris
>
>
> This seems counter intuitive to me, I can understand that C assigned that
> behavior somewhat arbitrar...