public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gmail.com>
To: "gcc-bugzilla@gcc.gnu.org" <gcc-bugzilla@gcc.gnu.org>
Cc: "gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>
Subject: Re: [Bug libstdc++/44663] New: missed GXX_EXPERIMENTAL guards in <tr1/tuple>?
Date: Fri, 25 Jun 2010 14:18:00 -0000 [thread overview]
Message-ID: <C8A6E60A-508C-42BB-AE52-B102E807AF82@gmail.com> (raw)
In-Reply-To: <bug-44663-7667@http.gcc.gnu.org/bugzilla/>
On Jun 25, 2010, at 3:49 AM, "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org
> wrote:
> hi,
>
> the latest llvm/clang++ reports an error during parsing <tr1/tuple>
> included from <tr1/functional>:
Both of these are c++0x only headers and really are only supported
when compiling in c++0x mode.
>
> In file included from t00.cpp:1:
> In file included from /usr/include/c++/4.5.0/tr1/functional:39:
> /usr/include/c++/4.5.0/tr1/tuple:68:30: error: variadic templates
> are only
> allowed in C++0x
> template<int _Idx, typename... _Elements>
>
> afaics there's no #ifdef __GXX_EXPERIMENTAL... guards but...
>
> http://gcc.gnu.org/onlinedocs/libstdc++/manual/bk01pt01ch01.html#manual.intro.status.standard.200x
>
> (...)
> In this implementation -std=gnu++0x or -std=c++0x flags must be used
> to enable language and library features. The pre-defined symbol
> __GXX_EXPERIMENTAL_CXX0X__ is used to check for the presence of
> the required flag.
> (...)
>
>
> --
> Summary: missed GXX_EXPERIMENTAL guards in <tr1/tuple>?
> Product: gcc
> Version: 4.5.1
> Status: UNCONFIRMED
> Severity: normal
> Priority: P3
> Component: libstdc++
> AssignedTo: unassigned at gcc dot gnu dot org
> ReportedBy: pluto at agmk dot net
> GCC host triplet: x86_64-gnu-linux
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44663
>
next prev parent reply other threads:[~2010-06-25 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 10:49 pluto at agmk dot net
2010-06-25 11:09 ` [Bug libstdc++/44663] " redi at gcc dot gnu dot org
2010-06-25 11:55 ` redi at gcc dot gnu dot org
2010-06-25 11:59 ` paolo dot carlini at oracle dot com
2010-06-25 14:18 ` pinskia at gmail dot com
2010-06-25 14:18 ` Andrew Pinski [this message]
2010-06-25 14:23 ` paolo dot 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=C8A6E60A-508C-42BB-AE52-B102E807AF82@gmail.com \
--to=pinskia@gmail.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-bugzilla@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).