Re: Problem on i386 with -fpic -fomit-frame-pointer

[Richard Henderson <rth at cygnus dot com>]

On Sun, Oct 11, 1998 at 01:24:50AM -0600, Jeffrey A Law wrote:
> I suspect there probably are still cases where reload is going to try to put
> those constants in the constant pool.
> 
> That's generally what reload does with a constant when it gets confused.  It
> just drops it into memory and loads it into an appropriate register.

It shouldn't.  One of the changes Bernd and I iterated on a bit ago
was to get reload to actually emit the instructions that generate
these constants.  And aside from 0.0 and 1.0, everything else should
have been dropped to memory during rtl generation.

A question might be -- if something somewhere is still wrong, or
breaks in the future, how to be sure that reload will abort rather
than silently generate bad code in this instance.


r~