public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/100186] lto-wrapper.c assumes std::thread Date: Wed, 21 Apr 2021 16:56:40 +0000 [thread overview] Message-ID: <bug-100186-4-GbOBjzdAgV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100186-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100186 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Yeah, only GCC 10 and later seems to define std::thread in <thread> unconditionally, older releases made it conditional on #ifdef _GLIBCXX_HAS_GTHREADS or on #if defined(_GLIBCXX_HAS_GTHREADS) && defined(_GLIBCXX_USE_C99_STDINT_TR1) The fact that something is in C++11 doesn't mean we can assume it in GCC, while GCC 4.8.x which we still want to support had roughly complete C++11 FE support, I think the libstdc++ side wasn't there yet.
next prev parent reply other threads:[~2021-04-21 16:56 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-21 15:52 [Bug bootstrap/100186] New: " dje at gcc dot gnu.org 2021-04-21 15:52 ` [Bug bootstrap/100186] " dje at gcc dot gnu.org 2021-04-21 16:09 ` dje at gcc dot gnu.org 2021-04-21 16:56 ` jakub at gcc dot gnu.org [this message] 2021-04-21 17:17 ` redi at gcc dot gnu.org 2021-04-21 17:19 ` dje at gcc dot gnu.org 2021-04-21 17:59 ` marxin at gcc dot gnu.org 2021-04-21 18:03 ` marxin at gcc dot gnu.org 2021-04-21 18:33 ` jakub at gcc dot gnu.org 2021-04-21 19:35 ` marxin at gcc dot gnu.org 2021-04-21 19:38 ` marxin at gcc dot gnu.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=bug-100186-4-GbOBjzdAgV@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).