From: Andrew Pinski <pinskia@gmail.com>
To: "Ellcey, Steve" <Steve.Ellcey@cavium.com>
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: glibc test tst-thread_local1.cc fails to compile with latest GCC
Date: Wed, 19 Oct 2016 17:51:00 -0000 [thread overview]
Message-ID: <CA+=Sn1kPvYaYstdjdCkVshBCJU3KQxAeUxrLMm74hLmonqOTxA@mail.gmail.com> (raw)
In-Reply-To: <SN2PR0701MB1071127508DE3F0D1174CF3AF5D20@SN2PR0701MB1071.namprd07.prod.outlook.com>
On Wed, Oct 19, 2016 at 10:45 AM, Ellcey, Steve <Steve.Ellcey@cavium.com> wrote:
> I have built the latest glibc sources with a ToT GCC and am trying to run the glibc testsuite now. I ran into a couple of
> new warnings that I fixed (locally) and am now looking at nptl/tst-thread_local1.cc which dies with:
>
> tst-thread_local1.cc:172:7: error: ‘thread’ is not a member of ‘std’
> std::thread thr{[func] {func (nullptr);}};
>
> Does anyone know what is going on here? If I compile a small test program:
>
> #include <thread>
> int main(int, char **){
> std::thread tt;
> }
>
> With G++ 5.4 (using -std=c++11) this test program compiles. but with ToT GCC, it dies with:
>
> g++ -std=c++11 thread.cc -lpthread -o x
> thread.cc: In function ‘int main(int, char**)’:
> thread.cc:5:5: error: ‘thread’ is not a member of ‘std’
> std::thread tt;
> ^~~
> thread.cc:5:5: note: suggested alternative: ‘fread’
> std::thread tt;
> ^~~
> fread
I Just tested it with revision 241328 of GCC, it works ...
apinski@apinski-ss1:~/src/local4$ ./tools/bin/g++ t88.cc -std=c++11 -mabi=ilp32
apinski@apinski-ss1:~/src/local4$ ./a.out
Thanks,
Andrew
>
>
> Is there some C++ standard change that I am not aware of or some other header file I need to include?
>
> Steve Ellcey
next prev parent reply other threads:[~2016-10-19 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 17:45 Ellcey, Steve
2016-10-19 17:51 ` Andrew Pinski [this message]
2016-10-21 16:03 ` Jonathan Wakely
2016-10-21 16:07 ` Steve Ellcey
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='CA+=Sn1kPvYaYstdjdCkVshBCJU3KQxAeUxrLMm74hLmonqOTxA@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=Steve.Ellcey@cavium.com \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sourceware.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).