public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "florin at iucha dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/97936] [11 Regression] 30_threads/latch/3.cc hangs Date: Mon, 18 Jan 2021 03:38:02 +0000 [thread overview] Message-ID: <bug-97936-4-pVq1Q5hHq9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97936-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97936 --- Comment #14 from florin at iucha dot net --- For reference: $ /opt/gcc11/bin/g++-11 -v Using built-in specs. COLLECT_GCC=/opt/gcc11/bin/g++-11 COLLECT_LTO_WRAPPER=/opt/gcc11/libexec/gcc/x86_64-linux-gnu/11.0.0/lto-wrapper Target: x86_64-linux-gnu Configured with: ../gcc/configure --prefix=/opt/gcc11 --with-local-prefix=/opt/gcc11 --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --program-suffix=-11 --with-abi=m64 --with-default-libstdcxx-abi=new --with-linker-hash-style=gnu --with-tune=generic --disable-multilib --disable-nls --disable-vtable-verify --enable-c99 --enable-checking=release --enable-__cxa_atexit --enable-default-pie --enable-gnu-indirect-function --enable-gnu-unique-object --enable-languages=c,c++ --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-linker-build-id --enable-long-long --enable-shared --enable-threads=posix Thread model: posix Supported LTO compression algorithms: zlib gcc version 11.0.0 20210110 (experimental) (GCC)
next prev parent reply other threads:[~2021-01-18 3:38 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-22 0:34 [Bug libstdc++/97936] New: " hjl.tools at gmail dot com 2020-11-22 0:43 ` [Bug libstdc++/97936] " redi at gcc dot gnu.org 2020-11-22 0:44 ` hjl.tools at gmail dot com 2020-11-22 13:17 ` hjl.tools at gmail dot com 2020-11-22 13:19 ` hjl.tools at gmail dot com 2020-11-23 7:33 ` rguenth at gcc dot gnu.org 2020-11-24 23:41 ` cvs-commit at gcc dot gnu.org 2020-11-25 1:30 ` redi at gcc dot gnu.org 2020-11-25 10:33 ` cvs-commit at gcc dot gnu.org 2020-11-25 11:01 ` redi at gcc dot gnu.org 2020-11-25 12:32 ` cvs-commit at gcc dot gnu.org 2020-11-25 18:37 ` cvs-commit at gcc dot gnu.org 2020-11-25 18:43 ` redi at gcc dot gnu.org 2020-11-26 16:25 ` cvs-commit at gcc dot gnu.org 2020-11-27 10:56 ` redi at gcc dot gnu.org 2021-01-18 3:36 ` florin at iucha dot net 2021-01-18 3:38 ` florin at iucha dot net [this message] 2021-04-09 7:58 ` rguenth at gcc dot gnu.org 2021-04-09 17:23 ` rodgertq at gcc dot gnu.org 2021-04-27 11:39 ` [Bug libstdc++/97936] [11/12 " jakub at gcc dot gnu.org 2021-04-27 12:03 ` redi at gcc dot gnu.org 2022-06-21 15:12 ` sumbera at volny dot cz 2022-07-06 1:15 ` rodgertq at gcc dot gnu.org 2023-04-27 13:03 ` 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-97936-4-pVq1Q5hHq9@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).