Re: [AD] gcc 3.x workaround.

["Eric Botcazou" <ebotcazou@xxxxxxxxxx>]

> i have removed all instances of -fomit-frame-pointer optimalisations from
> the makefiles in preparation for the stable release. please don't touch
> this.

I disagree: the x86 platform is well-known for its scarcity of registers, so
having one less register to use may have significant performance hits.

Moreover, I don't see why we would do that for the Mingw32 port, the BeOS
port and the QNX port since AFAIK they haven't yet seen the first
incarnation of the gcc 3.0.x series.

> that goes for the djgpp port as well!

Not very fair, given that the DJGPP workers (especially Andris Pavenis)
filed a GCC bug report for us (PR 4763 contains the code generated for
ustrzcpy() from src/unicode.c), then backported the fix and re-released the
gcc 3.0.2 packages.

The fix has been applied to the 3.0 branch on November 10, so it is highly
likely to be in the official 3.0.3 release.

> at a later date this optimalisation can be put back and replaced by a FAQ
> entry explaining that gcc 3.0 >< 3.0.3 has an optimiser which generates
> invalid code for some optimalisations used by allegro.

docs/build/djgpp.txt already states that gcc 3.0.x (0 <= x <= 1) can't
properly compile Allegro.

And it would be IMHO more clever to add a little test in the configure
script under Linux/Unix in order to disable -fomit-frame-pointer if needed.

--
Eric Botcazou
ebotcazou@xxxxxxxxxx