This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Why no strings in error messages?
- From: Ian Lance Taylor <iant at google dot com>
- To: Bradley Lucier <lucier at math dot purdue dot edu>
- Cc: GCC Mailing List <gcc at gcc dot gnu dot org>
- Date: Wed, 26 Aug 2009 06:30:44 -0700
- Subject: Re: Why no strings in error messages?
- References: <DEE925A1-D6D6-4423-B174-69FA6B7DD29F@math.purdue.edu>
Bradley Lucier <lucier@math.purdue.edu> writes:
> I've never seen the answer to the following question: Why do some
> versions of gcc that I build not have string substitutions in error
> messages?
Perhaps you configured with --disable-intl?
> So, is -fschedule-insns an option to be avoided?
-fschedule-insns should be avoided on Intel architectures. In general
-fschedule-insns tends to increase register lifespan, and because of the
small number of available registers this can sometimes befuddle the
register allocator, especially when asm instructions as used.
On PPC -fschedule-insns is normally beneficial, and it is turned on by
-O2.
Ian