Displaying 3 results from an estimated 3 matches for "image_rel_i386_rel32".
2017 Jun 06
2
[newbie] trouble with global variables and CreateLoad/Store in JIT
...$64, %esp
> 8: 89 e0 movl %esp, %eax
> a: c7 00 00 00 00 00 movl $0, (%eax)
> 0000000c: IMAGE_REL_I386_DIR32 _foo
> 10: e8 00 00 00 00 calll 0 <_setfoo+0x11>
> 00000011: IMAGE_REL_I386_REL32 _debugPointer
> 15: 89 e1 movl %esp, %ecx
> 17: c7 01 00 00 00 00 movl $0, (%ecx)
> 00000019: IMAGE_REL_I386_DIR32 _foo
> 1d: 89 44 24 3c movl %eax, 60(%esp)
> 21: 89 54 24 38 movl %e...
2017 Jun 07
2
[newbie] trouble with global variables and CreateLoad/Store in JIT
...89 e0 movl %esp, %eax
>>> a: c7 00 00 00 00 00 movl $0, (%eax)
>>> 0000000c: IMAGE_REL_I386_DIR32 _foo
>>> 10: e8 00 00 00 00 calll 0 <_setfoo+0x11>
>>> 00000011: IMAGE_REL_I386_REL32 _debugPointer
>>> 15: 89 e1 movl %esp, %ecx
>>> 17: c7 01 00 00 00 00 movl $0, (%ecx)
>>> 00000019: IMAGE_REL_I386_DIR32 _foo
>>> 1d: 89 44 24 3c movl %eax, 60(%esp)
>>>...
2017 Jun 06
2
[newbie] trouble with global variables and CreateLoad/Store in JIT
On Mon, Jun 5, 2017 at 1:34 PM, Nikodemus Siivola <
nikodemus at random-state.net> wrote:
> Uh. Turns out that if I hide the pointer to @foo from LLVM by passing it
> through an opaque identity function ... then everything works fine.
>
> Is this a bug in LLVM or is there some magic involving globals I'm
> misunderstanding?
>
This looks like a bug in the handling of