public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/107221] [13 Regression] libstdc++ EH no matching function __gnu_cxx::__scoped_lock::__scoped_lock
Date: Tue, 11 Oct 2022 19:04:22 +0000 [thread overview]
Message-ID: <bug-107221-4-HeTQbuatZ5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107221-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107221
David Edelsohn <dje at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2022-10-11
Status|UNCONFIRMED |NEW
--- Comment #1 from David Edelsohn <dje at gcc dot gnu.org> ---
Where is __GTHREADS defined now?
-#include <bits/c++config.h>
...
+#ifdef __GTHREADS
// A single mutex controlling emergency allocations.
__gnu_cxx::__mutex emergency_mutex;
+ using __scoped_lock = __gnu_cxx::__scoped_lock;
+#else
+ int emergency_mutex = 0;
+ struct __scoped_lock { explicit __scoped_lock(int) { } };
+#endif
next prev parent reply other threads:[~2022-10-11 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 18:54 [Bug bootstrap/107221] New: " dje at gcc dot gnu.org
2022-10-11 19:04 ` dje at gcc dot gnu.org [this message]
2022-10-11 19:15 ` [Bug bootstrap/107221] " redi at gcc dot gnu.org
2022-10-11 19:36 ` cvs-commit at gcc dot gnu.org
2022-10-12 8:47 ` 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-107221-4-HeTQbuatZ5@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).