public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nathan@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	johnc@parore.tait.co.nz, nobody@gcc.gnu.org
Subject: Re: c++/7721: Very simple (but incorrect) template chokes g++
Date: Fri, 13 Sep 2002 14:27:00 -0000	[thread overview]
Message-ID: <20020913212723.8247.qmail@sources.redhat.com> (raw)

Synopsis: Very simple (but incorrect) template chokes g++

State-Changed-From-To: open->analyzed
State-Changed-By: nathan
State-Changed-When: Fri Sep 13 14:27:23 2002
State-Changed-Why:
    confirmed as a regression

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7721


             reply	other threads:[~2002-09-13 21:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-13 14:27 nathan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-11 11:28 gdr
2002-10-08 15:36 Pop Sébastian
2002-09-29  7:46 Gabriel Dos Reis
2002-09-29  3:46 Pop Sébastian
2002-08-26  1:46 John Carter

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=20020913212723.8247.qmail@sources.redhat.com \
    --to=nathan@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=johnc@parore.tait.co.nz \
    --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).