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: Preparsing sprintf format strings

From: Joe Buck <Joe dot Buck at synopsys dot COM>
To: "Kaveh R. GHAZI" <ghazi at caip dot rutgers dot edu>
Cc: Heikki Linnakangas <heikki at enterprisedb dot com>, gcc at gcc dot gnu dot org
Date: Wed, 10 Oct 2007 15:21:13 -0700
Subject: Re: Preparsing sprintf format strings
References: <470A2788.8080408@enterprisedb.com> <Pine.GSO.4.58.0710091648140.1868@caipclassic.rutgers.edu> <20071010151610.GA15665@synopsys.com> <Pine.GSO.4.58.0710101614290.17506@caipclassic.rutgers.edu>

On Wed, Oct 10, 2007 at 04:22:45PM -0400, Kaveh R. GHAZI wrote:
> > But these things are rarely going to be a huge win, and I get
> > the impression that competing compiler developers only do them
> > when they help with standard benchmarks.
> 
> Their loss.  I agree with avoiding these micro opts when they cause bloat.
> But when you win in both size and speed, IMHO we should do it.

Certainly.  I think anything that turns one call into one cheaper
call will always win, and we already do a bit of that (as you say,
this wins for both size and speed).

References:
- Preparsing sprintf format strings
  - From: Heikki Linnakangas
- Re: Preparsing sprintf format strings
  - From: Kaveh R. GHAZI
- Re: Preparsing sprintf format strings
  - From: Joe Buck
- Re: Preparsing sprintf format strings
  - From: Kaveh R. GHAZI

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