search for: javajitopcode

...task? Az I see, some of the problems can be fixed with an appropriate typedef/macro declaration, but in VMCore/JavaObject.cpp some lowlevel bitmanipulation is used, to mark object references as locked - as I believe. BR, Zsombor p.s this fixes a typo in the current svn trunk $ svn diff VMCore/JavaJITOpcodes.cpp Index: VMCore/JavaJITOpcodes.cpp =================================================================== --- VMCore/JavaJITOpcodes.cpp (revision 52951) +++ VMCore/JavaJITOpcodes.cpp (working copy) @@ -1008,7 +1008,7 @@ Value* val2 = popAsInt(); Value* val1 = popAsInt();...

...n appropriate > typedef/macro declaration, but in VMCore/JavaObject.cpp some lowlevel > bitmanipulation is used, to mark object references as locked - as I > believe. > > BR, > Zsombor > > > p.s > this fixes a typo in the current svn trunk > > $ svn diff VMCore/JavaJITOpcodes.cpp > Index: VMCore/JavaJITOpcodes.cpp > =================================================================== > --- VMCore/JavaJITOpcodes.cpp (revision 52951) > +++ VMCore/JavaJITOpcodes.cpp (working copy) > @@ -1008,7 +1008,7 @@ > Value* val2 = popAsInt(); >...

Hi, I am wondering how I can get the JIT'd llvm IR during VMKit execution. I am stuck in precompiling phase (when loading library classes), and I am facing various problems. If I can log the JIT'd llvm IR (from Java bytecode), that would be convenient. I turned on --enable-debug, but it doesn't seem very helpful at this stage. Any other suggestion is welcome. Thanks very much.

Duncan Sands wrote: >> One approach would be to simply duplicate the code in the 'finally' >> block for each exit, but that seems sub-optimal. It would be better, I >> think, to set a state variable before entering the 'finally' block, and >> then have it do a switch instruction at the end and transfer to the >> appropriate block. >>