public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <wolfgang.bangerth@iwr.uni-heidelberg.de>
To: mmitchel@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: optimization/2938: [Regression vs 2.95] Optimization with -O1causes near infinite time
Date: Mon, 02 Jul 2001 07:26:00 -0000 [thread overview]
Message-ID: <20010702142601.13220.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR optimization/2938; it has been noted by GNATS.
From: Wolfgang Bangerth <wolfgang.bangerth@iwr.uni-heidelberg.de>
To: Mark Mitchell <mark@codesourcery.com>
Cc: "mmitchel@gcc.gnu.org" <mmitchel@gcc.gnu.org>,
"gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>,
"gcc-gnats@gcc.gnu.org" <gcc-gnats@gcc.gnu.org>
Subject: Re: optimization/2938: [Regression vs 2.95] Optimization with -O1
causes near infinite time
Date: Mon, 2 Jul 2001 16:21:11 +0200 (MET DST)
Mark Mitchell wrote:
> I have just checked in a patch that I think will really work this time.
> Would you check that it fixes the problem for you, and then tell me
> which PRs I can close?
It indeed does this time :-) optimization/2938 is already closed, but
c++/615 isn't, so please close that. (615 was the original report, 2938
was kind of a re-post that showed the problem in a more pronounced way).
Many thanks & best regards
Wolfgang
PS: Checked on Solaris2.7 and Linux.
-------------------------------------------------------------------------
Wolfgang Bangerth email: wolfgang.bangerth@iwr.uni-heidelberg.de
www: http://gaia.iwr.uni-heidelberg.de/~wolf
next reply other threads:[~2001-07-02 7:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 7:26 Wolfgang Bangerth [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-25 23:46 Wolfgang Bangerth
2001-06-25 6:16 Wolfgang 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=20010702142601.13220.qmail@sourceware.cygnus.com \
--to=wolfgang.bangerth@iwr.uni-heidelberg.de \
--cc=gcc-prs@gcc.gnu.org \
--cc=mmitchel@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).