public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, lucier@math.purdue.edu, nobody@gcc.gnu.org Subject: Re: optimization/2001: Inordinately long compile times in reload CSE regs Date: Mon, 25 Nov 2002 15:03:00 -0000 [thread overview] Message-ID: <20021119145450.20330.qmail@sources.redhat.com> (raw) Synopsis: Inordinately long compile times in reload CSE regs State-Changed-From-To: feedback->analyzed State-Changed-By: bangerth State-Changed-When: Tue Nov 19 06:54:48 2002 State-Changed-Why: Brad says this still happens. Since it is a regression w.r.t. 2.95, I raise its priority. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=2001
next reply other threads:[~2002-11-19 14:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-25 15:03 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-25 15:09 Wolfgang Bangerth 2002-11-24 14:28 bangerth 2001-04-01 0:00 lucier 2001-04-01 0:00 Brad Lucier
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=20021119145450.20330.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=lucier@math.purdue.edu \ --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).