This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Why no strings in error messages?

From: Paolo Bonzini <bonzini at gnu dot org>
To: Michael Meissner <meissner at linux dot vnet dot ibm dot com>, Ian Lance Taylor <iant at google dot com>, Bradley Lucier <lucier at math dot purdue dot edu>, GCC Mailing List <gcc at gcc dot gnu dot org>
Date: Wed, 26 Aug 2009 20:38:51 +0200
Subject: Re: Why no strings in error messages?
Newsgroups: gmane.comp.gcc.devel
References: <DEE925A1-D6D6-4423-B174-69FA6B7DD29F@math.purdue.edu> <m33a7e66t7.fsf@google.com> <20090826163748.GA31407@hungry-tiger.westford.ibm.com>

When I worked at AMD, I was starting to suspect that it may be more beneficial
to re-enable the first schedule insns pass if you were compiling in 64-bit
mode, since you have more registers available, and the new registers do not
have hard wired uses, which in the past always meant a lot of spills (also, the
default floating point unit is SSE instead of the x87 stack).  I never got
around to testing this before AMD and I parted company.

Unfortunately, hardwired use of %ecx for shifts is still enough to kill -fschedule-insns on AMD64.

Paolo

Follow-Ups:
- Re: Why no strings in error messages?
  - From: Bradley Lucier

References:
- Why no strings in error messages?
  - From: Bradley Lucier
- Re: Why no strings in error messages?
  - From: Ian Lance Taylor
- Re: Why no strings in error messages?
  - From: Michael Meissner

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]