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++/108288] Deadlock when using -fno-elide-constructor + -D_GLIBCXX_DEBUG=1 + -std=c++11 Date: Thu, 05 Jan 2023 14:40:54 +0000 [thread overview] Message-ID: <bug-108288-4-IsZfblZvW2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108288-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108288 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- This was my reproducer, although it doesn't deadlock without the hack to use a single mutex for all objects. #define _GLIBCXX_DEBUG 1 #include <vector> int main() { std::vector<int> v{1,2,3}; auto i = v.begin(); return *i++; }
next prev parent reply other threads:[~2023-01-05 14:40 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-04 20:22 [Bug libstdc++/108288] New: " simon.marchi at polymtl dot ca 2023-01-05 14:33 ` [Bug libstdc++/108288] " redi at gcc dot gnu.org 2023-01-05 14:35 ` redi at gcc dot gnu.org 2023-01-05 14:39 ` redi at gcc dot gnu.org 2023-01-05 14:40 ` redi at gcc dot gnu.org [this message] 2023-01-05 16:49 ` simon.marchi at polymtl dot ca 2023-01-05 17:12 ` redi at gcc dot gnu.org 2023-01-05 17:38 ` simon.marchi at polymtl dot ca 2023-01-05 17:43 ` redi at gcc dot gnu.org 2023-01-05 17:55 ` simon.marchi at polymtl dot ca 2023-01-06 11:53 ` cvs-commit at gcc dot gnu.org 2023-01-06 11:54 ` redi at gcc dot gnu.org 2023-01-15 16:07 ` cvs-commit at gcc dot gnu.org 2023-07-07 10:06 ` rguenth 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-108288-4-IsZfblZvW2@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).