public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/23691] [4.0 Regression] `mpl_::bool_<false>::value' is not a valid template argument for type `bool' because it is a non-constant expression
Date: Fri, 02 Sep 2005 13:20:00 -0000 [thread overview]
Message-ID: <20050902131957.32440.qmail@sourceware.org> (raw)
In-Reply-To: <20050902090119.23691.caolanm@redhat.com>
------- Additional Comments From jakub at gcc dot gnu dot org 2005-09-02 13:19 -------
Well, it is not 4.0.2, as 4.0.2 has not been released. FSF version.c contains
prerelease string which somewhat explains that it is really not yet official
4.0.2, but we use the version also for rpm version where claiming the compiler is
4.0.2 would be misleading. It is something between 4.0.1 and 4.0.2.
For any RH version.c, the date printed is the date of merge from the
corresponding upstream gcc-X_Y-branch which is I guess the most important
info for you.
This bug is actually something I asked Caolan to file here, because I knew
there were no C++ changes between the 2 compilers where it broke other than
the changes brought from a new gcc-4_0-branch merge.
--
What |Removed |Added
----------------------------------------------------------------------------
Known to work|4.0.0 4.1.0 |4.0.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23691
next prev parent reply other threads:[~2005-09-02 13:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 9:01 [Bug c++/23691] New: ‘mpl_::bool_<false>::value’ is not a valid template argument for type ‘bool’ " caolanm at redhat dot com
2005-09-02 9:05 ` [Bug c++/23691] " caolanm at redhat dot com
2005-09-02 12:02 ` pinskia at gcc dot gnu dot org
2005-09-02 13:05 ` [Bug c++/23691] `mpl_::bool_<false>::value' is not a valid template argument for type `bool' " jakub at gcc dot gnu dot org
2005-09-02 13:07 ` [Bug c++/23691] [4.0 Regression] " pinskia at gcc dot gnu dot org
2005-09-02 13:11 ` pinskia at gcc dot gnu dot org
2005-09-02 13:13 ` pinskia at gcc dot gnu dot org
2005-09-02 13:20 ` jakub at gcc dot gnu dot org [this message]
2005-09-02 13:21 ` jakub at gcc dot gnu dot org
2005-09-02 13:23 ` jakub at gcc dot gnu dot org
2005-09-02 13:30 ` pinskia at gcc dot gnu dot org
2005-09-02 13:41 ` pinskia at gcc dot gnu dot org
2005-09-02 15:47 ` pinskia at gcc dot gnu dot org
2005-09-02 16:40 ` pinskia at gcc dot gnu dot org
2005-09-02 16:42 ` matz at suse dot de
2005-09-02 22:52 ` pinskia at gcc dot gnu dot org
2005-09-07 20:03 ` bangerth at dealii dot org
2005-09-07 20:07 ` pinskia at gcc dot gnu dot org
2005-09-07 20:12 ` bangerth at dealii dot org
2005-09-08 16:51 ` bangerth at dealii dot org
2005-09-08 18:57 ` cvs-commit at gcc dot gnu dot org
2005-09-08 19:00 ` cvs-commit at gcc dot gnu dot org
2005-09-08 19:02 ` mmitchel at gcc dot gnu dot org
2005-09-08 19:04 ` mmitchel at gcc dot gnu dot org
2005-09-12 19:01 ` cvs-commit 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=20050902131957.32440.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).