public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/66146] call_once not C++11-compliant on ppc64le Date: Thu, 11 Feb 2021 13:29:57 +0000 [thread overview] Message-ID: <bug-66146-4-IflxyAKJXM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66146-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66146 --- Comment #40 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Libor Bukata from comment #39) > (In reply to Libor Bukata from comment #38) > > (In reply to Jonathan Wakely from comment #34) > > > Untested sketch of a solution for Solaris and BSDs: > > > https://gcc.gnu.org/pipermail/gcc-patches/2020-November/557928.html > > > > Thank you for the patch, I will test it on Solaris > > and let you know when I have the results. > > Patched GCC master with Jonathan's patch, but unfortunately it is not > compilable on Solaris 11: > In file included from > /gcc_nightly/build/sparcv9/sparcv9-sun-solaris2.11/libstdc++-v3/include/ > sparcv9-sun-solaris2.11/bits/c++config.h:568, > from > /gcc_nightly/build/sparcv9/sparcv9-sun-solaris2.11/libstdc++-v3/include/ > cassert:43, > from > /gcc_nightly/gcc-11.0.0-master/libstdc++-v3/include/precompiled/stdc++.h:33: > /gcc_nightly/build/sparcv9/sparcv9-sun-solaris2.11/libstdc++-v3/include/ > mutex:861:10: error: token "{" is not valid in preprocessor expressions > 861 | || _GLIBCXX_COMPAT_PTHREAD_ONCE_T > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > In file included from > /gcc_nightly/build/sparcv9/sparcv9-sun-solaris2.11/libstdc++-v3/include/ > sparcv9-sun-solaris2.11/bits/c++config.h:568, > from > /gcc_nightly/build/sparcv9/sparcv9-sun-solaris2.11/libstdc++-v3/include/ > cassert:43, > from > /gcc_nightly/gcc-11.0.0-master/libstdc++-v3/include/precompiled/stdc++.h:33: > /gcc_nightly/build/sparcv9/sparcv9-sun-solaris2.11/libstdc++-v3/include/ > mutex:861:10: error: token "{" is not valid in preprocessor expressions > 861 | || _GLIBCXX_COMPAT_PTHREAD_ONCE_T > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Oops, that should be: || defined _GLIBCXX_COMPAT_PTHREAD_ONCE_T to test if the macro is defined, rather than testing its value. > In file included from > /gcc_nightly/build/sparcv9/sparcv9-sun-solaris2.11/libstdc++-v3/include/ > future:38, > from > /gcc_nightly/gcc-11.0.0-master/libstdc++-v3/include/precompiled/stdc++.h:105: > /gcc_nightly/build/sparcv9/sparcv9-sun-solaris2.11/libstdc++-v3/include/ > mutex:675:15: error: explicitly defaulted function 'constexpr > std::once_flag::once_flag()' cannot be declared 'constexpr' because the > implicit declaration is not 'constexpr': > 675 | constexpr once_flag() noexcept = default; > | ^~~~~~~~~ > /gcc_nightly/build/sparcv9/sparcv9-sun-solaris2.11/libstdc++-v3/include/ > mutex:699:12: note: defaulted constructor calls non-'constexpr' > 'std::once_flag::_Once::_Once()' > 699 | struct _Once _GLIBCXX_COMPAT_PTHREAD_ONCE_T; This one's a bit trickier. The struct needs a default constructor that initializes all its members, but then it can't be used in the union. I'll provide a new patch when I get a chance to look into it.
next prev parent reply other threads:[~2021-02-11 13:29 UTC|newest] Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-14 18:31 [Bug libstdc++/66146] New: " andrey.vul at gmail dot com 2015-05-15 8:55 ` [Bug libstdc++/66146] " redi at gcc dot gnu.org 2015-05-15 15:12 ` andrey.vul at gmail dot com 2015-05-15 17:40 ` msebor at gcc dot gnu.org 2015-05-15 20:31 ` redi at gcc dot gnu.org 2015-05-19 17:36 ` andrey.vul at gmail dot com 2015-05-20 0:11 ` msebor at gcc dot gnu.org 2015-05-20 14:12 ` redi at gcc dot gnu.org 2015-05-20 14:36 ` bugdal at aerifal dot cx 2015-05-20 14:46 ` jakub at gcc dot gnu.org 2015-05-20 14:47 ` redi at gcc dot gnu.org 2015-05-20 14:51 ` bugdal at aerifal dot cx 2020-05-07 11:56 ` jakub at gcc dot gnu.org 2020-06-27 18:18 ` pdimov at gmail dot com 2020-07-09 8:52 ` redi at gcc dot gnu.org 2020-08-27 13:56 ` kisha-nik at mail dot ru 2020-11-03 14:51 ` redi at gcc dot gnu.org 2020-11-03 18:45 ` cvs-commit at gcc dot gnu.org 2020-11-03 18:46 ` redi at gcc dot gnu.org 2020-11-03 18:46 ` redi at gcc dot gnu.org 2020-11-03 20:17 ` redi at gcc dot gnu.org 2020-12-17 9:08 ` tschwinge at gcc dot gnu.org 2020-12-17 9:58 ` redi at gcc dot gnu.org 2020-12-17 14:03 ` cvs-commit at gcc dot gnu.org 2021-02-04 15:16 ` libor.bukata at oracle dot com 2021-02-11 8:00 ` libor.bukata at oracle dot com 2021-02-11 13:29 ` redi at gcc dot gnu.org [this message] 2021-02-15 13:03 ` redi at gcc dot gnu.org 2021-02-15 14:13 ` bugdal at aerifal dot cx 2021-02-15 15:00 ` redi at gcc dot gnu.org 2021-02-15 17:08 ` bugdal at aerifal dot cx 2021-02-15 17:10 ` fw at gcc dot gnu.org 2021-02-15 17:30 ` bugdal at aerifal dot cx 2021-03-16 12:39 ` cvs-commit at gcc dot gnu.org 2021-04-07 6:22 ` unlvsur at live dot com 2021-04-07 10:03 ` redi at gcc dot gnu.org 2021-04-19 10:40 ` redi at gcc dot gnu.org 2021-04-27 11:37 ` jakub at gcc dot gnu.org 2021-07-28 7:04 ` rguenth at gcc dot gnu.org 2022-02-10 23:20 ` redi at gcc dot gnu.org 2022-02-10 23:29 ` redi at gcc dot gnu.org 2022-12-02 1:25 ` lh_mouse at 126 dot com 2022-12-03 9:26 ` redi at gcc dot gnu.org 2024-03-14 11:55 ` cvs-commit at gcc dot gnu.org 2024-03-18 11:22 ` cvs-commit at gcc dot gnu.org 2024-03-18 14:03 ` cvs-commit at gcc dot gnu.org 2024-05-13 9:04 ` [Bug libstdc++/66146] call_once not C++11-compliant iains 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-66146-4-IflxyAKJXM@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).