public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andreemalcher at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100584] New: [modules] ICE when using import <thread>; with std::jthread Date: Thu, 13 May 2021 11:15:08 +0000 [thread overview] Message-ID: <bug-100584-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100584 Bug ID: 100584 Summary: [modules] ICE when using import <thread>; with std::jthread Product: gcc Version: 11.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: andreemalcher at gmail dot com Target Milestone: --- $ cat thread.cpp import <iostream>; // Compiles & runs fine with include or if order if swapped with next line #include <thread> int main() { std::jthread t{[]{}}; // Compiles & runs fine with std::thread } $ g++ -fmodules-ts -std=c++20 -c -x c++-system-header iostream$ g++ -fmodules-ts -std=c++20 -o prog thread.cpp -pthread during IPA pass: visibility thread.cpp:6:1: internal compiler error: in function_and_variable_visibility, at ipa-visibility.c:712 6 | } | ^ 0x1702697 internal_error(char const*, ...) ???:0 0x64082b fancy_abort(char const*, int, char const*) ???:0 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <file:///usr/share/doc/gcc-11/README.Bugs> for instructions. If you replace std::jthread with std::thread (optionally, with corresponding join()), it compiles just fine. Also, the order of import vs. include seems to matter (see comment in code). Same ICE for import <string>;, for example, but not for import <vector>;. Haven't tried others.
next reply other threads:[~2021-05-13 11:15 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-13 11:15 andreemalcher at gmail dot com [this message] 2022-10-12 9:36 ` [Bug c++/100584] " 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-100584-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).