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, nobody@gcc.gnu.org,
	sebor@roguewave.com
Subject: Re: c++/3882: gcc 3.0 error referencing a variable in its initializer expression in template code
Date: Wed, 01 Aug 2001 05:05:00 -0000	[thread overview]
Message-ID: <20010801120549.14745.qmail@sourceware.cygnus.com> (raw)

Synopsis: gcc 3.0 error referencing a variable in its initializer expression in template code

State-Changed-From-To: open->analyzed
State-Changed-By: nathan
State-Changed-When: Wed Aug  1 05:05:49 2001
State-Changed-Why:
    confirmed as a 2.95 regression

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3882&database=gcc


             reply	other threads:[~2001-08-01  5:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-01  5:05 nathan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-18 15:37 jason
2002-03-18  5:12 jason
2001-07-30 12:46 sebor

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=20010801120549.14745.qmail@sourceware.cygnus.com \
    --to=nathan@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=sebor@roguewave.com \
    /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).