public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/1687: Extreme compile time regression from 2.95.2
Date: Fri, 11 Apr 2003 19:06:00 -0000	[thread overview]
Message-ID: <20030411190600.18848.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/1687; it has been noted by GNATS.

From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: gcc-gnats@gcc.gnu.org, kelley.cook@home.com,
	gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	bangerth <bangerth@ticam.utexas.edu>
Cc:  
Subject: Re: c++/1687: Extreme compile time regression from 2.95.2
Date: Fri, 11 Apr 2003 20:57:21 +0200

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=1687
 
 I cannot reproduce this with:
 - gcc-3.3 (GCC) 3.3 20030407 (prerelease) or
 - gcc-3.4 (GCC) 3.4 20030411 (experimental).
 
 Both give subsecond compile times.  Which is particularly nice
 because it means that we can say at least one positive thing about
 compile time performance of 3.3 (this is a regression that is not
 marked as one for some reason...).
 
 Wolfgang, you were the last to re-confirm the PR, do you still
 see it?
 
 Greetz
 Steven
 
 
 


             reply	other threads:[~2003-04-11 19:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-11 19:06 Steven Bosscher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-11 21:46 Steven Bosscher
2003-04-11 19:36 Wolfgang Bangerth
2002-11-20 18:58 Wolfgang Bangerth
2002-11-10 14:16 Zack Weinberg
2002-11-10 13:56 Wolfgang Bangerth
2001-04-01  0:00 Zack Weinberg
2001-04-01  0:00 Zack Weinberg
2001-04-01  0:00 Zack Weinberg
2001-04-01  0:00 Zack Weinberg

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=20030411190600.18848.qmail@sources.redhat.com \
    --to=s.bosscher@student.tudelft.nl \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /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).