public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jason@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jason@gcc.gnu.org, sebor@roguewave.com Subject: Re: c++/3870: gcc 3.0 bogus error specializing a template function Date: Mon, 18 Mar 2002 06:35:00 -0000 [thread overview] Message-ID: <20020318143530.7959.qmail@sources.redhat.com> (raw) Synopsis: gcc 3.0 bogus error specializing a template function State-Changed-From-To: analyzed->closed State-Changed-By: jason State-Changed-When: Mon Mar 18 06:35:28 2002 State-Changed-Why: Fixed for 3.1 by * cp-tree.h (struct saved_scope): Add last_parms field. * decl.c (maybe_push_to_top_level): Save last_function_parms. (pop_from_top_level): Restore it. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3870
next reply other threads:[~2002-03-18 14:35 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-18 6:35 jason [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-18 4:24 jason 2001-08-01 5:17 nathan 2001-07-29 19:06 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=20020318143530.7959.qmail@sources.redhat.com \ --to=jason@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@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: linkBe 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).