public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/29607] [DR 224] [4.1/4.2 Regression] dependent name with base classes
Date: Fri, 27 Oct 2006 01:28:00 -0000 [thread overview]
Message-ID: <20061027012814.26411.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29607-5724@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from pinskia at gcc dot gnu dot org 2006-10-27 01:28 -------
(In reply to comment #9)
> one of those patches introduces the regression on the 4.1 branch
The backport of Nathan's patch caused it, though DR 224 is the questionable
problem here and reading the standard currently (without that Defect report),
this is actually invalid code.
The testcase in PR 29469 comment #5, shows that Defect report is bogus and
needs to be rethought.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29607
next prev parent reply other threads:[~2006-10-27 1:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 17:42 [Bug c++/29607] New: code fails to build with 4.1 20061020, which built with 20060901 debian-gcc at lists dot debian dot org
2006-10-26 17:43 ` [Bug c++/29607] " debian-gcc at lists dot debian dot org
2006-10-26 17:59 ` pinskia at gcc dot gnu dot org
2006-10-26 18:22 ` debian-gcc at lists dot debian dot org
2006-10-26 19:52 ` pinskia at gcc dot gnu dot org
2006-10-26 20:07 ` pinskia at gcc dot gnu dot org
2006-10-26 20:12 ` [Bug c++/29607] [DR 224] [4.1/4.2 Regression] dependent name with base classes pinskia at gcc dot gnu dot org
2006-10-26 23:23 ` debian-gcc at lists dot debian dot org
2006-10-27 1:12 ` janis at gcc dot gnu dot org
2006-10-27 1:23 ` debian-gcc at lists dot debian dot org
2006-10-27 1:28 ` pinskia at gcc dot gnu dot org [this message]
2006-11-13 3:38 ` [Bug c++/29607] [DR 224] [4.1/4.2/4.3 " mmitchel at gcc dot gnu dot org
2007-02-14 9:21 ` mmitchel at gcc dot gnu dot org
2007-12-16 23:20 ` steven at gcc dot gnu dot org
2008-01-08 16:26 ` steven at gcc dot gnu dot org
2008-01-08 16:30 ` steven at gcc dot gnu dot org
2008-01-21 16:42 ` jsm28 at gcc dot gnu dot org
2008-07-04 21:44 ` [Bug c++/29607] [DR 224] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2009-03-03 21:14 ` jason at gcc dot gnu dot org
2009-03-04 12:06 ` rguenth at gcc dot gnu dot org
2009-03-04 14:48 ` jason at gcc dot gnu dot org
2009-03-04 18:43 ` jason at gcc dot gnu dot org
2009-03-04 19:38 ` jason at gcc dot gnu dot org
2009-03-04 19:41 ` jason at gcc dot gnu dot org
2009-04-03 17:32 ` jason 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=20061027012814.26411.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).