search for: bci_146

...trace_bytecode 2694: ori 4, 21, 6516 2695: li 3, 140 2696: bl trace_bytecode 2697: ori 4, 21, 7724 2698: li 3, 143 2699: bl trace_bytecode 2700: cmpwi 0, 14, 127 2701: bgt 0, BB10_65 # bci_202 2702: BB10_45: # bci_146 2703: lis 26, 3984 2704: ori 21, 26, 6556 2705: li 3, 146 2706: mr 4, 21 2707: bl trace_bytecode 2708: li 3, 148 2709: mr 4, 21 2710: bl trace_bytecode 2711: ori 4, 26, 7712 2712: li 3, 150 2713:...

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

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/