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: middle-end/3973: GCC fails to bootstrap with 80+160MB memory / optimization Date: Tue, 07 Jan 2003 00:16:00 -0000 [thread overview] Message-ID: <20030107001601.5209.qmail@sources.redhat.com> (raw) The following reply was made to PR middle-end/3973; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org> Subject: Re: middle-end/3973: GCC fails to bootstrap with 80+160MB memory / optimization Date: Mon, 6 Jan 2003 18:06:34 -0600 (CST) > > I would not even pretend I would disagree with you on the matter of > > compile time and memory consumption, but every time I brought this up > > (even with numbers from our own project), nothing really happens. > > Have you created high-priority PRs for such projects? That might be > better than this PR... The project is 200k lines of template heavy C++. Not exactly a smaller testcase. I occasionally filed reports for cases where compile time exploded (and these were fixed mostly), but the general trend of 3.3 being (more than) twice as slow as 2.95 for example is unchecked, and I don't have a simple testcase for that, unfortunately. In fact, there are testcases already around: the automatic SPEC testers also log daily compile times for fixed programs. Every once in a while someone notices that something gets slower and sometimes even can point to a particular patch, but the general trend is not broken by that. > > So what should we do? > > ...which I agree to close. I'll do it, but only with a certain amount of reluctance :-( W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth/
next reply other threads:[~2003-01-07 0:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-07 0:16 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-07 0:06 bangerth 2003-01-06 23:56 Gerald Pfeifer 2003-01-06 22:46 Wolfgang Bangerth 2002-12-27 11:56 Gerald Pfeifer 2002-12-10 16:19 bangerth 2001-08-09 7:16 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=20030107001601.5209.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).