Displaying 3 results from an estimated 3 matches for "048b0000".
2009 Jan 22
1
[LLVMdev] JIT debug dumps [Was Re: Load from abs address generated bad code on LLVM 2.4]
...(char**)&Args[0]);
>
> This also gives you control over optimizations and codegen options,
Yes, thanks. It's a slightly weird hack, but it works perfectly. :-)
"-debug-only=jit" generates just a binary dump, like this:
JIT: Binary code:
JIT: 00000000: 4a04b848 000000ca 048b0000 c320
whereas "-debug-only=x86-emitter" generates this:
%RAX<def> = MOV64ri <ga:poo1>
%EAX<def> = MOV32rm %RAX<kill>, 1, %reg0, 0, Mem:LD(4,4) [poo1 + 0]
RET %EAX<imp-use,kill>
which may be more useful.
Can I put in a request some machine-independent names...
2009 Jan 21
0
[LLVMdev] Load from abs address generated bad code on LLVM 2.4
On Jan 21, 2009, at 4:15 AM, Andrew Haley wrote:
>> That should work fine, just use "jit" instead of "x86-emitter" as the
>> debug type.
>
> That's impossible: CurrentDebugType is now private; it appears
> nowhere in the installed headers. I can't find any public interface
> to allow a JIT to set it.
Ah ok. I'd suggest doing what llvm-gcc
2009 Jan 21
3
[LLVMdev] Load from abs address generated bad code on LLVM 2.4
Chris Lattner wrote:
> On Jan 20, 2009, at 2:10 AM, Andrew Haley wrote:
>
>> Chris Lattner wrote:
>>> On Jan 19, 2009, at 7:55 AM, Andrew Haley wrote:
>>>
>>>> This is x86_64. I have a problem where an absolute memory load
>>>> The current LLVM trunk does not have this bug. This seems quite a
>>>> nasty
>>>> bug; is