public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "malat at debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/103629] [11/12/13 Regression] wrong-code when mixing mutex with visibility=hidden Date: Fri, 17 Mar 2023 07:36:36 +0000 [thread overview] Message-ID: <bug-103629-4-CDVsq1U03w@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103629-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103629 --- Comment #27 from Mathieu Malaterre <malat at debian dot org> --- Symptom may go away with: * https://github.com/AcademySoftwareFoundation/openvdb/pull/1589
next prev parent reply other threads:[~2023-03-17 7:36 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-09 13:25 [Bug c++/103629] New: Possible miscompilation triggered by -fvisibility=hidden mathieu.malaterre at gmail dot com 2021-12-09 13:30 ` [Bug c++/103629] " marxin at gcc dot gnu.org 2021-12-09 13:32 ` pinskia at gcc dot gnu.org 2021-12-09 13:38 ` mathieu.malaterre at gmail dot com 2021-12-09 13:45 ` pinskia at gcc dot gnu.org 2021-12-09 14:03 ` mathieu.malaterre at gmail dot com 2021-12-09 14:15 ` pinskia at gcc dot gnu.org 2021-12-09 14:23 ` mathieu.malaterre at gmail dot com 2021-12-10 13:11 ` mathieu.malaterre at gmail dot com 2021-12-10 13:13 ` [Bug c++/103629] Possible miscompilation triggered by pthread + exception mathieu.malaterre at gmail dot com 2021-12-10 13:20 ` [Bug c++/103629] Possible miscompilation visible using " pinskia at gcc dot gnu.org 2021-12-10 13:22 ` [Bug libstdc++/103629] " pinskia at gcc dot gnu.org 2021-12-10 14:33 ` redi at gcc dot gnu.org 2021-12-10 15:01 ` redi at gcc dot gnu.org 2021-12-10 15:09 ` redi at gcc dot gnu.org 2021-12-10 15:10 ` redi at gcc dot gnu.org 2021-12-10 15:13 ` redi at gcc dot gnu.org 2021-12-10 15:28 ` redi at gcc dot gnu.org 2021-12-19 22:52 ` pinskia at gcc dot gnu.org 2021-12-19 22:53 ` [Bug libstdc++/103629] [11/12 Regression] " pinskia at gcc dot gnu.org 2022-01-04 9:04 ` rguenth at gcc dot gnu.org 2022-04-21 7:50 ` rguenth at gcc dot gnu.org 2022-08-24 12:14 ` [Bug libstdc++/103629] [11/12/13 " malat at debian dot org 2022-08-24 12:14 ` malat at debian dot org 2022-08-24 12:16 ` malat at debian dot org 2022-08-24 12:28 ` [Bug libstdc++/103629] [11/12/13 Regression] wrong-code when mixing mutex with visibility=hidden malat at debian dot org 2022-08-24 12:30 ` malat at debian dot org 2023-03-17 7:36 ` malat at debian dot org [this message] 2023-05-29 10:06 ` [Bug libstdc++/103629] [11/12/13/14 " jakub 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-103629-4-CDVsq1U03w@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).