Re: gcc 4.0.0 optimization vs. id strings (RCS, SCCS, etc.)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bruce Lilly wrote: > Hi, > > Earlier versions of gcc retain static character strings in object files > which can be used for identification via ident (RCS) or what (SCCS). > Gcc 4.0.0 removes them above optimization level 1. Global strings > are reta

Re: Some small optimization issues with gcc 4.0 20050418

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 James E Wilson wrote: > Sebastian Biallas wrote: > >> You don't need to reserve a stack slot for the return address on x86. >> The stack slot will be allocated implicitly by the "call" instruction. > > OK, t

Re: Some small optimization issues with gcc 4.0 20050418

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 James E Wilson wrote: > Sebastian Biallas wrote: > >> But I noticed some smaller optimization issues on x86, and on of them is >> a regression to gcc 3.3 so I'm reporting this here. Accept my apologies >> if this is al

Some small optimization issues with gcc 4.0 20050418

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello! I just tested the prerelease of gcc 4.0 (to see whether my programs still compile and work), and I must say: Congratulations, no real problems so far. But I noticed some smaller optimization issues on x86, and on of them is a regression to gcc