public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/96817] __cxa_guard_acquire unsafe against dynamically loaded pthread Date: Thu, 27 Aug 2020 12:58:59 +0000 [thread overview] Message-ID: <bug-96817-4-HzZFtos8zo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96817-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96817 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- it's been always that way - but yes, people repeatedly fall into this trap
next prev parent reply other threads:[~2020-08-27 12:58 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-27 12:32 [Bug libstdc++/96817] New: " yshuiv7 at gmail dot com 2020-08-27 12:48 ` [Bug libstdc++/96817] " yshuiv7 at gmail dot com 2020-08-27 12:48 ` redi at gcc dot gnu.org 2020-08-27 12:53 ` yshuiv7 at gmail dot com 2020-08-27 12:58 ` rguenth at gcc dot gnu.org [this message] 2020-08-27 13:05 ` yshuiv7 at gmail dot com 2020-08-27 13:06 ` yshuiv7 at gmail dot com 2020-08-27 13:15 ` redi at gcc dot gnu.org 2020-08-27 13:23 ` redi at gcc dot gnu.org 2020-08-27 13:26 ` yshuiv7 at gmail dot com 2020-08-27 13:34 ` redi at gcc dot gnu.org 2020-08-27 14:02 ` redi at gcc dot gnu.org 2020-08-27 14:04 ` redi at gcc dot gnu.org 2020-09-25 18:11 ` redi at gcc dot gnu.org 2020-09-25 19:55 ` redi at gcc dot gnu.org 2020-09-25 20:37 ` yshuiv7 at gmail dot com 2020-09-25 20:40 ` yshuiv7 at gmail dot com 2020-09-26 19:41 ` cvs-commit at gcc dot gnu.org 2020-10-25 9:27 ` rimvydas.jas at gmail dot com 2020-10-25 22:08 ` redi at gcc dot gnu.org 2020-11-04 15:34 ` cvs-commit at gcc dot gnu.org 2020-11-04 15:36 ` redi 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-96817-4-HzZFtos8zo@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).