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

Jeffrey A Law law@cygnus.com
Sun Oct 11 00:26:00 GMT 1998


  In message <Pine.SOL.3.90.981008144357.2965E-100000@matula.informatik.rwth-aa
chen.de>you write:
  > I'm not entirely certain about what is going on.  We are definitely having
  > some weird problems still.  First of all, I'd like to see the original test
  > case that led to the Jul 26 change, if someone still has it.
http://www.cygnus.com/ml/egcs-bugs/1998-Jun/0345.html

There are random messages about this bug in egcs, egcs-bugs and egcs-patches
in June and July.

  > That we're now creating such insns might in fact be good news, because
  > that means we might be able to undo HJ's change: if reload no longer
  > needs to put standard 387 constants into the constant pool, the original
  > motivation for the change is probably gone.  But I'm not sure, since I
  > don't have the original test case.
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.

jeff



More information about the Gcc mailing list