[RFH] - Less than optimal code compiling 252.eon -O2 for x86

Fariborz Jahanian fjahanian@apple.com
Thu Jun 30 21:30:00 GMT 2005


On Jun 30, 2005, at 12:47 PM, Steven Bosscher wrote:

>
> Well, maybe so, but it would be a pretty lame workaround.  Why are you
> so worried about bugs?  This flag was always disabled at -O1, and we
> have never seen any bug reports that got fixed with -fforced-mem.  And
> besides, it is better to fix bugs than to work around them.
>
> Making the option a nop, issuing a warning in 4.1 and removing the
> option completely for gcc 4.2 looks like a very reasonable approach to
> me.
>

OK. This seems to be the consensus and I will prepare a patch base on  
that.

- Thanks, fariborz

> Gr.
> Steven
>
>



More information about the Gcc mailing list