public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/1687: Extreme compile time regression from 2.95.2 Date: Sun, 10 Nov 2002 13:56:00 -0000 [thread overview] Message-ID: <20021110215602.16344.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/1687; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: gcc-gnats@gcc.gnu.org, <kelley.cook@home.com>, <gcc-bugs@gcc.gnu.org>, <pbienst@gcc.gnu.org>, Zack Weinberg <zack@codesourcery.com> Cc: Subject: Re: c++/1687: Extreme compile time regression from 2.95.2 Date: Sun, 10 Nov 2002 15:51:12 -0600 (CST) Zack, you had a patch for this problem, as mentioned in the audit. Do you know whether it was applied? I cannot find it in the ChangeLogs. At any rate, I get reasonable compile times with -O2: tmp/g> time /home/bangerth/bin/gcc-3.3x-pre/bin/gcc -O2 -c x.cc real 0m0.168s user 0m0.150s sys 0m0.010s tmp/g> time /home/bangerth/bin/gcc-3.3x-pre/bin/gcc -O2 -c x.cc real 0m0.261s user 0m0.150s sys 0m0.000s However, at -O3 it still takes forever, now with both C and C++, which seems a further regression (since previously this held only for C++). I don't trust this for various reasons, so maybe someone can confirm this with -O3? Regards Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-11-10 21:56 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-10 13:56 Wolfgang Bangerth [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 2003-04-11 19:06 Steven Bosscher 2002-11-20 18:58 Wolfgang Bangerth 2002-11-10 14:16 Zack Weinberg 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=20021110215602.16344.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --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: linkBe 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).