public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com> 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 14:16:00 -0000 [thread overview] Message-ID: <20021110221601.25388.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/1687; it has been noted by GNATS. From: Zack Weinberg <zack@codesourcery.com> To: Wolfgang Bangerth <bangerth@ticam.utexas.edu> Cc: gcc-gnats@gcc.gnu.org, kelley.cook@home.com, gcc-bugs@gcc.gnu.org, pbienst@gcc.gnu.org, Zack Weinberg <zack@codesourcery.com> Subject: Re: c++/1687: Extreme compile time regression from 2.95.2 Date: Sun, 10 Nov 2002 14:14:13 -0800 On Sun, Nov 10, 2002 at 03:51:12PM -0600, Wolfgang Bangerth wrote: > > 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. Yes, the patch was applied. It's in cp/ChangeLog: 2001-04-24 Zack Weinberg <zackw@stanford.edu> * cp/optimize.c: Include hashtab.h. (struct inline_data): Add tree_pruner. (expand_call_inline, expand_calls_inline): Use it when calling walk_tree. (optimize_function): Initialize and free tree_pruner. This code is now in tree-inline.c, by the way > 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? C being slow is a consequence of its using the tree-based inliner (previously only C++ did). I don't know why -O3 would cause further trouble. You could build cc1plus profiled (make clean in both libiberty and gcc, make all in libiberty with CFLAGS="-g -O2 -profile", make cc1plus in gcc with CFLAGS="-g -O2 -profile"), run it on the test case, and take a look at the gprof output. zw
next reply other threads:[~2002-11-10 22:16 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-10 14:16 Zack Weinberg [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 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=20021110221601.25388.qmail@sources.redhat.com \ --to=zack@codesourcery.com \ --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).