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: optimization/6798: [3.2/3.3/3.4 regression] very long compile time with large case-statement
Date: Wed, 12 Mar 2003 14:46:00 -0000 [thread overview]
Message-ID: <20030312144601.25454.qmail@sources.redhat.com> (raw)
The following reply was made to PR optimization/6798; it has been noted by GNATS.
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
Cc: s.bosscher@student.tudelft.nl, <gcc-gnats@gcc.gnu.org>,
<gcc-bugs@gcc.gnu.org>, <eggert@twinsun.com>
Subject: Re: optimization/6798: [3.2/3.3/3.4 regression] very long compile
time with large case-statement
Date: Wed, 12 Mar 2003 08:41:34 -0600 (CST)
> > Volker, you said you saw this on Linux? I don't see this bug on
> > i586-linux, so I hope you can confirm this so we can close this PR, or
> > else we should try to find out if this is a target-specific problem.
> >
> > Greetz
> > Steven
>
> Sorry, but that was Wolfgang and not me
Yes, I could reproduce this with mainline. I just checked again, it's fine
now on mainline, but it still takes forever on the 3.3 branch. However,
for well known reasons I can't update my 3.3 copy, which is still of
2003-03-05. Likewise, my 3.2 copy (from 2003-01-24).
So, it seems as if this is fixed on mainline. I'll change the synopsis
accordingly. Can anyone double check with the other two branches and newer
versions than mine?
Thanks
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ticam.utexas.edu
www: http://www.ticam.utexas.edu/~bangerth/
next reply other threads:[~2003-03-12 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 14:46 Wolfgang Bangerth [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-12 12:16 Volker Reichelt
2003-03-11 20:56 Steven Bosscher
2003-02-19 13:16 Steven Bosscher
2003-01-15 16:27 bangerth
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=20030312144601.25454.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: 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).