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: Wed, 20 May 2015 14:47:00 -0000 [thread overview]
Message-ID: <bug-66146-4-BU5QtkakwQ@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 #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #4)
> Thanks, Martin. So maybe something like this:
>
> --- a/libstdc++-v3/include/std/mutex
> +++ b/libstdc++-v3/include/std/mutex
> @@ -726,7 +738,17 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
> __set_once_functor_lock_ptr(&__functor_lock);
> #endif
>
> +#ifdef __powerpc__
> + int __e;
> + __try {
> + __e = __gthread_once(&__once._M_once, &__once_proxy);
> + } __catch(...) {
> + __once._M_once = once_flag{}._M_once;
N.B. This won't work because it races, and may not even compile (if e.g.
pthread_once_t has a const member)
next prev parent reply other threads:[~2015-05-20 14:47 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 [this message]
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
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-BU5QtkakwQ@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: 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).