public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: jason@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: middle-end/10336: [3.3/3.4 regression] ICE with -Wunreachable-code
Date: Tue, 29 Apr 2003 18:46:00 -0000	[thread overview]
Message-ID: <20030429184600.19275.qmail@sources.redhat.com> (raw)

The following reply was made to PR middle-end/10336; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: Giovanni Bajo <giovannibajo@libero.it>
Cc: s.bosscher@student.tudelft.nl, <gcc-gnats@gcc.gnu.org>,
   Jason Merrill <jason@redhat.com>, <mark@codesourcery.com>
Subject: Re: middle-end/10336: [3.3/3.4 regression] ICE with -Wunreachable-code
Date: Tue, 29 Apr 2003 13:44:09 -0500 (CDT)

 > Ah, sorry. Confirmed with 3.3/3.4 (C frontend) and 3.4 only (C++ frontend).
 > I think the synopsis should be changed to report the 3.3 regression.
 
 OK, I did that.
 
 Mark, can you add this to your watch-list? My gut tells me that we will 
 get _lots_ of PRs from this one otherwise. Jason's got a tentative patch, 
 so we might have a resolution there soon.
 
 Jason, can you make sure this goes into 3.3 as well if the patch works 
 and Mark agrees?
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:            bangerth@ices.utexas.edu
                                www: http://www.ices.utexas.edu/~bangerth/
 
 
 


             reply	other threads:[~2003-04-29 18:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-29 18:46 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-30 17:42 jason
2003-04-15  6:36 Steven Bosscher
2003-04-15  3:36 Jason Merrill
2003-04-12 12:49 steven

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=20030429184600.19275.qmail@sources.redhat.com \
    --to=bangerth@ices.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jason@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).