search for: dump59

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?

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/

...91: lis 25, 3984 4892: lis 14, dump58 at ha 4893: ori 13, 25, 6556 4894: li 3, 630 4895: mr 4, 13 4896: bl trace_bytecode 4897: la 3, dump58 at l(14) 4898: mr 4, 27 4899: bl print_value 4900: lis 14, dump59 at ha 4901: li 3, 632 4902: mr 4, 13 4903: bl trace_bytecode 4904: lis 13, dump60 at ha 4905: la 3, dump59 at l(14) 4906: mr 4, 26 4907: bl print_value -------------- next part -------------- A non-text attachment was scrubbed......

Hi all, I'm trying to figure out a weird bug I'm seeing. I'm hoping it's something simple in my IR but I can't see anything wrong so I'm hoping someone here can see something. I'm using LLVM to compile Java bytecode into native functions. My code keeps track of the Java local variables in an array of llvm::Value pointers which get phi'd up at various points. The