public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo dot carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/39777] Template behaviour when a template class has a member template class deriving from its container
Date: Wed, 15 Apr 2009 17:04:00 -0000 [thread overview]
Message-ID: <20090415170421.21412.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39777-17578@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from paolo dot carlini at oracle dot com 2009-04-15 17:04 -------
For the record, the Intel compiler - which I trust much more than DM, sorry -
behaves the same as GCC. I strongly believe GCC is correct. I even think we
have something closed about this issue, let me see if I find it...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39777
next prev parent reply other threads:[~2009-04-15 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 15:18 [Bug c++/39777] New: " pietro dot braione at polimi dot it
2009-04-15 15:21 ` [Bug c++/39777] " pietro dot braione at polimi dot it
2009-04-15 15:40 ` pinskia at gcc dot gnu dot org
2009-04-15 17:04 ` paolo dot carlini at oracle dot com [this message]
[not found] <bug-39777-4@http.gcc.gnu.org/bugzilla/>
2011-10-19 1:52 ` paolo.carlini at oracle dot com
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=20090415170421.21412.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).