public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rs2740 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/111050] [11/12/13/14 Regression] ABI break in _Hash_node_value_base since GCC 11 Date: Wed, 06 Sep 2023 18:15:30 +0000 [thread overview] Message-ID: <bug-111050-4-2KvmqhGLzt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111050-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111050 --- Comment #5 from TC <rs2740 at gmail dot com> --- Minimal example: $ cat lib1.cpp #include <unordered_set> #include <string> static std::unordered_set<std::string> set; void del(const std::string& s) { set.erase(s); } $ cat lib2.cpp #include <unordered_set> #include <string> static std::unordered_set<std::string> set; void add(const std::string& s) { set.emplace(s); } const std::string& get(const std::string& s) { return *set.find(s); } $ cat main.cpp #include <string> void add(const std::string&); void del(const std::string&); const std::string& get(const std::string&); int main() { add("foo"); del("bar"); (void) get("foo").size(); } $ g++-10 -std=c++17 lib1.cpp -c -o lib1.o $ g++-13 -std=c++17 lib2.cpp -c -o lib2.o $ g++-13 -std=c++17 main.cpp lib1.o lib2.o -o test $ ./test Segmentation fault (core dumped)
next prev parent reply other threads:[~2023-09-06 18:15 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-17 14:40 [Bug libstdc++/111050] New: " rs2740 at gmail dot com 2023-08-17 15:03 ` [Bug libstdc++/111050] " redi at gcc dot gnu.org 2023-08-18 6:42 ` rguenth at gcc dot gnu.org 2023-09-01 20:33 ` fdumont at gcc dot gnu.org 2023-09-01 23:17 ` rs2740 at gmail dot com 2023-09-02 7:20 ` fdumont at gcc dot gnu.org 2023-09-06 17:17 ` fdumont at gcc dot gnu.org 2023-09-06 18:15 ` rs2740 at gmail dot com [this message] 2023-09-06 18:19 ` rs2740 at gmail dot com 2023-09-08 17:04 ` rs2740 at gmail dot com 2023-09-11 11:52 ` redi at gcc dot gnu.org 2023-09-11 16:59 ` frs.dumont at gmail dot com 2023-09-12 15:54 ` john at drouhard dot dev 2023-09-12 16:07 ` redi at gcc dot gnu.org 2023-09-28 17:24 ` cvs-commit at gcc dot gnu.org 2023-10-02 20:44 ` cvs-commit at gcc dot gnu.org 2023-10-02 20:47 ` cvs-commit at gcc dot gnu.org 2023-10-02 20:48 ` cvs-commit at gcc dot gnu.org 2023-10-03 9:31 ` 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-111050-4-2KvmqhGLzt@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).