Patch for jump optimization

[Michael P. Hayes]

Jeffrey A Law writes:
 >   > I fixed the problem for GCC 2.8.0 by looking for safer places that
 >   > the insn could be inserted, and then only rejecting the optimisation
 >   > if it couldn't find a suitable place.
 >   > 
 > I must have missed that -- I didn't remember seeing any related changes go
 > into gcc-2.8.  I must have missed them.
 > 
 > Just so we're both clear, the stuff to handle constants in memory should be
 > OK right?

Yes, the stuff to handle conditional floating point loads and
conditional loads of constants in memory should be OK.  We could
probably generalise things to any operand supported by the backend.

Michael.