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: Bradley Lucier <lucier at math dot purdue dot edu>
To: Ian Lance Taylor <iant at google dot com>
Cc: Paolo Bonzini <bonzini at gnu dot org>, Michael Meissner <meissner at linux dot vnet dot ibm dot com>, GCC Mailing List <gcc at gcc dot gnu dot org>, Bradley Lucier <lucier at math dot purdue dot edu>
Date: Wed, 26 Aug 2009 21:30:12 -0400
Subject: Re: Why no strings in error messages?
References: <DEE925A1-D6D6-4423-B174-69FA6B7DD29F@math.purdue.edu> <m33a7e66t7.fsf@google.com> <20090826163748.GA31407@hungry-tiger.westford.ibm.com> <4A95813B.4010708@gnu.org> <1251313364.25086.194.camel@heine.math.purdue.edu> <m3ab1m2jza.fsf@google.com>

On Wed, 2009-08-26 at 17:12 -0700, Ian Lance Taylor wrote:

> If you are getting that kind of speedup (which I personally did not
> expect) then this is clearly worth pursuing.  It should be possible to
> make it work at least in 64-bit mode.  I recommend that you file a bug
> report or two for cases which fail when using -fschedule-insns.

Thanks, I've added some details of the speedup (with code differences)
to the end of PR33928 and I've reported the two different failures (for
x86-64 and ppc64) in PR41164 and PR41176.

Brad

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
- Re: Why no strings in error messages?
  - From: Paolo Bonzini
- Re: Why no strings in error messages?
  - From: Bradley Lucier
- Re: Why no strings in error messages?
  - From: Ian Lance Taylor

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