public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gnu.w2nnu at simplelogin dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105512] compilation with -fmodules-ts and std=c++20 leads to segfault Date: Sun, 18 Jun 2023 18:02:38 +0000 [thread overview] Message-ID: <bug-105512-4-W9qfvBjasL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105512-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105512 David Truby <gnu.w2nnu at simplelogin dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gnu.w2nnu at simplelogin dot com --- Comment #1 from David Truby <gnu.w2nnu at simplelogin dot com> --- I also see this issue and have a reproducer here: ---- main.cpp #include <iostream> #include <string> import test; int main() { std::cout << tester(); } ---- test.cpp module; #include <string> export module test; export std::string tester() { return "hello world\n"; } ---- Interestingly the issue also goes away if -D_GLIBCXX_USE_CXX11_ABI=0 is passed to both TUs so I suspect there's an issue with the module file not exporting the correct ABI for `std::string`
next prev parent reply other threads:[~2023-06-18 18:02 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-07 7:19 [Bug c++/105512] New: " deco33000 at yandex dot com 2023-06-18 18:02 ` gnu.w2nnu at simplelogin dot com [this message] 2023-09-08 20:12 ` [Bug c++/105512] " mail@gerrit-albrecht.de 2024-03-06 21:26 ` ppalka at gcc dot gnu.org 2024-03-07 21:24 ` cvs-commit at gcc dot gnu.org 2024-03-07 21:25 ` ppalka 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-105512-4-W9qfvBjasL@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).