public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: mmitchel@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/3083: C++ frontend consumes inacceptable amounts of CPU with -O3
Date: Tue, 23 Apr 2002 08:56:00 -0000	[thread overview]
Message-ID: <20020423155603.728.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/3083; it has been noted by GNATS.

From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: optimization/3083: C++ frontend consumes inacceptable amounts
 of CPU with -O3
Date: Tue, 23 Apr 2002 17:50:40 +0200 (CEST)

 http://gcc.gnu.org/ml/gcc/2002-04/msg01168.html contains a detailed
 analysis of build times, binary sizes and benchmark performance for
 GCC 2.95, 3.0, 3.0.3, the 3.1-branch as of 2002-04-22 (with various
 -finline-limit settings) and mainline as of 2002-04-22.
 


             reply	other threads:[~2002-04-23 15:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23  8:56 Gerald Pfeifer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-07  3:26 Gerald Pfeifer
2002-10-16 12:13 mmitchel
2001-07-11  3:48 gerald
2001-06-08  3:36 pfeifer

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=20020423155603.728.qmail@sources.redhat.com \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=mmitchel@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).