Displaying 5 results from an estimated 5 matches for "emitdataregionend".
2012 Oct 07
0
[LLVMdev] R_ARM_ABS32 disassembly with integrated-as
...t the core functionality to know how to mark data regions is there and works very well.
Hi Jim,
I'm trying to help Greg crack it down. From your recent commits, I
take it you're re-using a data-in-code detection previously used only
for ASM output, to object output, via the
EmitDataRegion/EmitDataRegionEnd.
I haven't looked too deep in the MC, but I'm supposing that will work
automatically when the output streamer is printing object code and
meets a non-code region, so in theory, changing MCELFStreamer
accordingly (overriding those functions in there) would take care of
data vs. code issue i...
2012 Oct 09
2
[LLVMdev] R_ARM_ABS32 disassembly with integrated-as
...w to mark data regions is there and works very well.
>
> Hi Jim,
>
> I'm trying to help Greg crack it down. From your recent commits, I
> take it you're re-using a data-in-code detection previously used only
> for ASM output, to object output, via the
> EmitDataRegion/EmitDataRegionEnd.
>
It's a bit more than that. Those Emit* methods are new for this support. There was spotty support for the raw $a/$t/$d stuff before, and this abstracted and extended it to support both asm and binary emission as well as added uses for the methods to the various bits in the ARM backend w...
2012 Oct 05
2
[LLVMdev] R_ARM_ABS32 disassembly with integrated-as
On Oct 5, 2012, at 12:15 AM, Tim Northover <t.p.northover at gmail.com> wrote:
> Hi Greg,
>
>> Is this a bug? If so, how can I fix it?
>
> It's somewhere between a bug and a quality-of-implementation issue.
> ARM often uses literal pools in the middle of code when it needs to
> materialize a large constant (or variable address more likely for
>
2012 Oct 10
0
[LLVMdev] R_ARM_ABS32 disassembly with integrated-as
...there and works very well.
>>
>> Hi Jim,
>>
>> I'm trying to help Greg crack it down. From your recent commits, I
>> take it you're re-using a data-in-code detection previously used only
>> for ASM output, to object output, via the
>> EmitDataRegion/EmitDataRegionEnd.
>>
>
> It's a bit more than that. Those Emit* methods are new for this support. There was spotty support for the raw $a/$t/$d stuff before, and this abstracted and extended it to support both asm and binary emission as well as added uses for the methods to the various bits in the A...
2012 Oct 10
2
[LLVMdev] R_ARM_ABS32 disassembly with integrated-as
...;>>
>>> Hi Jim,
>>>
>>> I'm trying to help Greg crack it down. From your recent commits, I
>>> take it you're re-using a data-in-code detection previously used only
>>> for ASM output, to object output, via the
>>> EmitDataRegion/EmitDataRegionEnd.
>>>
>>
>> It's a bit more than that. Those Emit* methods are new for this support. There was spotty support for the raw $a/$t/$d stuff before, and this abstracted and extended it to support both asm and binary emission as well as added uses for the methods to the various...