PATCH: interpreter.cc bug patch and performance improvements

[Tom Tromey]

>>>>> "Chris" == Chris Sears <cbsears_sf@yahoo.com> writes:

Chris> Run the cm3 benchmark on a stock 3.0.3. The performance will be
Chris> 644.  Comment out the insn_nop block and move the insn_nop
Chris> label in front of the first NEXT_INSN. Very simple, very dumb
Chris> optimization.

Doing this isn't really that important.
If you are concerned about the minor code duplication taken by the nop
processing, you can put `insn_nop:' before any other NEXT_INSN.  Try
folding it into insn_aconst_null.

Are `nop's common in Java bytecode?  I think `gcj -C' never generates
them.  I don't know about other compilers.

Anyway, if this gives you some kind of improvement, I'll check it in
even though it doesn't seem all that important.

Tom