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 bootstrap/107221] [13 Regression] libstdc++ EH no matching function __gnu_cxx::__scoped_lock::__scoped_lock Date: Tue, 11 Oct 2022 19:15:42 +0000 [thread overview] Message-ID: <bug-107221-4-Nopmjpmh3K@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 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |13.0 Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org Status|NEW |ASSIGNED --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- Same place it's always been defined, in gthr.h which is included by <ext/concurrence.h> And every other header includes <bits/c++config.h> i.e. all of these: #include <exception> // std::exception #include <new> // std::terminate #include <cstdlib> // std::malloc, std::free, std::strtoul #include <climits> // INT_MAX #include <bits/stl_function.h> // std::less #include "unwind-cxx.h" #if _GLIBCXX_HOSTED # include <string_view> // std::string_view # include <cstring> // std::strchr, std::memset # include <ext/concurrence.h> // __gnu_cxx::__mutex, __gnu_cxx::__scoped_lock #endif That's why I removed the unnecessary initial #include of it. This should fix it: --- a/libstdc++-v3/libsupc++/eh_alloc.cc +++ b/libstdc++-v3/libsupc++/eh_alloc.cc @@ -236,7 +236,7 @@ namespace void *pool::allocate (std::size_t size) noexcept { - __gnu_cxx::__scoped_lock sentry(emergency_mutex); + __scoped_lock sentry(emergency_mutex); // We need an additional size_t member plus the padding to // ensure proper alignment of data. size += offsetof (allocated_entry, data);
next prev parent reply other threads:[~2022-10-11 19:15 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 ` [Bug bootstrap/107221] " dje at gcc dot gnu.org 2022-10-11 19:15 ` redi at gcc dot gnu.org [this message] 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-Nopmjpmh3K@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).