public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "f.b.brokken at rug dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104202] New: when defining a std::string in a module implementation file using -O2 g++ segfaults Date: Mon, 24 Jan 2022 10:57:10 +0000 [thread overview] Message-ID: <bug-104202-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104202 Bug ID: 104202 Summary: when defining a std::string in a module implementation file using -O2 g++ segfaults Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: f.b.brokken at rug dot nl Target Milestone: --- Created attachment 52274 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52274&action=edit Output of the compiler (segfaults) when compiling 'mod.cc' Using the following main file (main.cc): --------------------------------- #include <iostream> import mod; int main() { std::cout << modstr << '\n'; } --------------------------------- defining the module mod interface in a separate file (zfirst.cc): --------------------------------- module; #include <string> export module mod; export extern std::string modstr; --------------------------------- and initializing modstr in a separate module implementation file (mod.cc): ------------------------------- module; #include <string> module mod; std::string modstr{ "hello" }; ------------------------------- compiles OK when using the following compiler options: --std=c++20 -Wall -Wextra -fno-strict-aliasing -fwrapv -fmodules-ts but when adding the option -O2 the compiler segfaults (compiler output is attached). Omitting the -Wextra -fno-strict-aliasing -fwrapv options makes no difference. The compilation was performed on a (yesterday) updated Debian testing distribution using g++ (Debian 12-20211217-1) 12.0.0 20211217 (experimental) [master r12-6027-g774269aa4b9] Copyright (C) 2021 Free Software Foundation, Inc. If you need any additional information, please let me know. Kind regards, Frank.
next reply other threads:[~2022-01-24 10:57 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-24 10:57 f.b.brokken at rug dot nl [this message] 2024-03-06 22:08 ` [Bug c++/104202] " 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-104202-4@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).