public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC still getting a lot slower
Date: Thu, 02 Jan 2003 10:59:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.51.0301021148470.62618@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20021231214116.GA1953@doctormoo>

On Tue, 31 Dec 2002, Nathanael Nerode wrote:
> Can we test compile time change of some *fixed* piece of code, perhaps?

PR 8361 (http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=8361),
which is basically the old PR 3083, is here for anyone to use. ;-)

Gerald

PS: It's no longer a completely fixed piece of code, as it's not possible
to have preprocessed source that is forwards or backwards compatible with
or from current mainline, but I have included two preprocessed files now.
-- 
Gerald "Jerry"   pfeifer@dbai.tuwien.ac.at   http://www.pfeifer.com/gerald/

  parent reply	other threads:[~2003-01-02 10:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-31 14:11 Nathanael Nerode
2002-12-31 14:49 ` Paul Jarc
2002-12-31 17:16 ` Diego Novillo
2003-01-02 10:59 ` Gerald Pfeifer [this message]
2003-01-02 14:21   ` Jan Hubicka
2003-01-03  0:21     ` Fergus Henderson
2003-01-03 14:05       ` Jan Hubicka
2003-01-03 10:33     ` Ben Elliston
     [not found] <1041382480.23232.35.camel@steven>
2003-01-02 14:24 ` Jan Hubicka
  -- strict thread matches above, loose matches on Subject: below --
2002-12-31 23:01 Ritzert
2002-12-31 16:14 Nathanael Nerode
2002-12-31 16:53 ` Paul Jarc
2002-12-31 13:44 Neil Booth
2002-12-31 13:47 ` Paolo Carlini
2002-12-31 13:48   ` Neil Booth
2002-12-31 13:55     ` Paolo Carlini
2002-12-31 14:00       ` Neil Booth
2002-12-31 20:22         ` David Edelsohn
2002-12-31 14:00   ` Diego Novillo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.BSF.4.51.0301021148470.62618@naos.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=gcc@gcc.gnu.org \
    --cc=neroden@twcny.rr.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).