public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/26122] [4.0/4.1 regression] Pure specifiers for templates causing trouble
Date: Wed, 17 May 2006 21:43:00 -0000 [thread overview]
Message-ID: <20060517214311.23137.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26122-1771@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from mmitchel at gcc dot gnu dot org 2006-05-17 21:43 -------
Fixed in 4.2.
I consider the issue in Comment #2 to be somewhere between a feature request
and a non-bug, as were there a dependent base class, it would not be possible
to tell if A::foo were virtual or not at the point of parsing the template.
--
mmitchel at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
Summary|[4.0/4.1/4.2 regression] |[4.0/4.1 regression] Pure
|Pure specifiers for |specifiers for templates
|templates causing trouble |causing trouble
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26122
next prev parent reply other threads:[~2006-05-17 21:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 12:25 [Bug c++/26122] New: [4.0/4.1/4.2 " reichelt at gcc dot gnu dot org
2006-02-06 12:46 ` [Bug c++/26122] " pinskia at gcc dot gnu dot org
2006-02-06 15:14 ` reichelt at gcc dot gnu dot org
2006-02-14 9:00 ` mmitchel at gcc dot gnu dot org
2006-02-18 9:51 ` mmitchel at gcc dot gnu dot org
2006-02-24 0:30 ` mmitchel at gcc dot gnu dot org
2006-04-11 23:00 ` mmitchel at gcc dot gnu dot org
2006-04-12 1:18 ` mmitchel at gcc dot gnu dot org
2006-04-12 1:19 ` mmitchel at gcc dot gnu dot org
2006-05-17 21:39 ` mmitchel at gcc dot gnu dot org
2006-05-17 21:43 ` mmitchel at gcc dot gnu dot org [this message]
2007-03-03 21:54 ` [Bug c++/26122] [4.0/4.1 " pinskia at gcc dot gnu dot org
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=20060517214311.23137.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).