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++/14007] [3.3/3.4 Regression] Incorrect use of const partial specialization for reference template argument
Date: Fri, 02 Apr 2004 16:59:00 -0000 [thread overview]
Message-ID: <20040402165951.27989.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040203195712.14007.austern@apple.com>
------- Additional Comments From mmitchel at gcc dot gnu dot org 2004-04-02 16:59 -------
I don't think we should be making any drastic changes right now.
The behavior in 3.4.0 is consistent with all releases from 3.0.x onwards.
Changing the semantics from these releases should not be done until we are
absolutely sure what the right behavior is.
In my opinion, that logic should apply to 3.3.4 as well. Making changes in
3.3.4 that will make it behave differently from 3.3.3 and from 3.4.0 would be a
mistake.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14007
next prev parent reply other threads:[~2004-04-02 16:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 19:57 [Bug c++/14007] New: " austern at apple dot com
2004-02-03 20:17 ` [Bug c++/14007] [3.3/3.4/3.5 Regression] " pinskia at gcc dot gnu dot org
2004-02-03 20:22 ` bangerth at dealii dot org
2004-02-03 20:26 ` pinskia at gcc dot gnu dot org
2004-02-15 12:45 ` gdr at gcc dot gnu dot org
2004-03-17 3:13 ` mmitchel at gcc dot gnu dot org
2004-03-17 18:23 ` austern at apple dot com
2004-03-17 19:02 ` nathan at codesourcery dot com
2004-03-19 14:27 ` nathan at gcc dot gnu dot org
2004-03-19 17:34 ` mmitchel at gcc dot gnu dot org
2004-03-19 17:39 ` gdr at integrable-solutions dot net
2004-03-19 18:12 ` austern at apple dot com
2004-03-19 18:19 ` pinskia at gcc dot gnu dot org
2004-03-19 18:20 ` pinskia at gcc dot gnu dot org
2004-04-02 10:07 ` nathan at gcc dot gnu dot org
2004-04-02 11:49 ` cvs-commit at gcc dot gnu dot org
2004-04-02 12:07 ` nathan at gcc dot gnu dot org
2004-04-02 12:10 ` giovannibajo at libero dot it
2004-04-02 15:13 ` [Bug c++/14007] [3.3/3.4 " gdr at integrable-solutions dot net
2004-04-02 15:29 ` nathan at gcc dot gnu dot org
2004-04-02 16:59 ` mmitchel at gcc dot gnu dot org [this message]
2004-04-02 17:39 ` bangerth at dealii dot org
2004-04-03 12:38 ` gdr at integrable-solutions dot net
2004-06-12 21:53 ` mmitchel at gcc dot gnu dot org
2004-06-13 10:02 ` nathan at gcc dot gnu dot org
2004-06-18 23:54 ` mmitchel at gcc dot gnu dot org
2004-06-19 9:00 ` nathan at gcc dot gnu dot org
2004-06-19 17:39 ` mark at codesourcery dot com
2004-06-21 12:46 ` cvs-commit at gcc dot gnu dot org
2004-06-21 12:46 ` nathan at gcc dot gnu dot org
2004-07-01 20:58 ` andreas dot meier_ at gmx dot de
2004-07-01 21:00 ` 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=20040402165951.27989.qmail@sources.redhat.com \
--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).