public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10486: Regression (ICE) in 3.3 branch due to recent patch.
Date: Fri, 25 Apr 2003 00:56:00 -0000	[thread overview]
Message-ID: <20030425005601.20302.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/10486; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: Carlo Wood <carlo@alinoe.com>
Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>
Subject: Re: c++/10486: Regression (ICE) in 3.3 branch due to recent patch.
Date: Thu, 24 Apr 2003 19:55:45 -0500 (CDT)

 > That test case indeed fails with my current 3.3.
 > I'll update again and retry.  Too bad I wasted a whole evening
 > condensing that test case while it was already fixed :/.
 
 What can I say -- I reduced and filed 10471, only to find out shortly 
 after that almost exactly the same bug had already been filed a couple of 
 hours earlier. The bug only existed about a day, and we now have 3 reports 
 about it...
 
 Can you ping me when you find that it is indeed fixed for your code? I'll 
 close the report then, if you want.
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:            bangerth@ices.utexas.edu
                                www: http://www.ices.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-04-25  0:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-25  0:56 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-25 15:08 bangerth
2003-04-25  1:56 Carlo Wood
2003-04-25  0:46 Carlo Wood
2003-04-25  0:20 bangerth
2003-04-25  0:06 carlo

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=20030425005601.20302.qmail@sources.redhat.com \
    --to=bangerth@ices.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).