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++/6758: [2003-01-01] ICE on nested type in template declaration
Date: Fri, 09 May 2003 00:36:00 -0000	[thread overview]
Message-ID: <20030509003600.15541.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: gcc-gnats@gcc.gnu.org, <gcc-bugs@gcc.gnu.org>,
   Giovanni Bajo <giovannibajo@libero.it>
Cc:  
Subject: Re: c++/6758: [2003-01-01] ICE on nested type in template declaration
Date: Thu, 8 May 2003 19:30:59 -0500 (CDT)

 > To be fair, the code is legal in 3.3 because of the implicit typename
 > extension. I guess this bug should be kept open (not analyzed - there is 
 > no testcase), in case someone wants to fix the ICE in the 3.3 branch.
 
 Well, why? The code ICEd since at least 2.95, so it's not a regression. 
 It's fixed on mainline. Bugs that are not regressions are not going to be 
 fixed on 3.3 branch, so why keep it open?
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:            bangerth@ices.utexas.edu
                                www: http://www.ices.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-05-09  0:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09  0:36 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-09  0:06 Giovanni Bajo
2003-05-08 23:22 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=20030509003600.15541.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).