Displaying 4 results from an estimated 4 matches for "trace_bytecod".
Did you mean:
trace_bytecode
2008 Jun 12
4
[LLVMdev] Possible miscompilation?
...148: iload
150: if_icmplt
185: aload
187: iload
189: iinc
192: iload
194: i2b
195: bastore
196: iinc
199: goto
630: iload
local_4_419 = 1
632: iload
local_5_420 = 261095424
local_4_419 = 1
-------------- next part --------------
2646: li 3, 632
2647: mr 4, 13
2648: bl trace_bytecode
2649: lis 13, dump57 at ha
2650: la 3, dump56 at l(14)
2651: mr 4, 26
2652: bl print_value
2653: la 3, dump57 at l(13)
2654: mr 4, 27
2655: bl print_value
2656: ori 4, 21, 7712
2657: li 3, 634
2658:...
2008 Jun 11
0
[LLVMdev] Possible miscompilation?
On 2008-06-11, at 13:16, Gary Benson wrote:
> Duncan Sands wrote:
>
>> Can you please attach IR which can be compiled to an executable
>> (and shows the problem).
>
> I've been generating functions using a builder and then compiling
> them with ExecutionEngine::getPointerToFunction(). Is there some way
> I can get compilable IR from that?
2008 Jun 11
2
[LLVMdev] Possible miscompilation?
Duncan Sands wrote:
> Can you please attach IR which can be compiled
> to an executable (and shows the problem).
I've been generating functions using a builder and then
compiling them with ExecutionEngine::getPointerToFunction().
Is there some way I can get compilable IR from that?
Cheers,
Gary
--
http://gbenson.net/
2008 Jun 11
3
[LLVMdev] Possible miscompilation?
...ing
it as far as I can see.
I attached a copy of the IR, both for the entire function and
for that section with only the blocks that are actually entered
as the function executes. grepping it for local_5 I don't see
anything that would modify it. There is some tracing code too,
the calls to @trace_bytecode and @print_value; the output from
that is also attached.
The bizarre thing is that if I add print the value of local_5
at every bytecode then everything is correct. This is what is
making me suspect a miscompilation.
Thanks in advance for any help!
Cheers,
Gary
--
http://gbenson.net/