public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "michael.kenzel at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114275] New: using std::thread within a templated function in a module fails to compile Date: Fri, 08 Mar 2024 02:04:29 +0000 [thread overview] Message-ID: <bug-114275-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114275 Bug ID: 114275 Summary: using std::thread within a templated function in a module fails to compile Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: michael.kenzel at gmail dot com Target Milestone: --- The following example will reproduce the issue: // A.ixx module; #include <thread> export module A; export void fun(auto&&) { std::thread([]{}).join(); } // main.cpp import A; int main() { fun(42); } build with g++ -std=c++23 -fmodules-ts -c -x c++ A.ixx g++ -std=c++23 -fmodules-ts main.cpp A.o results in ‘ /usr/include/c++/13/tuple:491: confused by earlier errors, bailing out
next reply other threads:[~2024-03-08 2:04 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-08 2:04 michael.kenzel at gmail dot com [this message] 2024-03-08 2:19 ` [Bug c++/114275] " pinskia at gcc dot gnu.org 2024-03-08 3:15 ` nshead at gcc dot gnu.org 2024-03-08 15:09 ` ppalka at gcc dot gnu.org 2024-03-08 15:23 ` law at gcc dot gnu.org 2024-03-17 9:02 ` nshead at gcc dot gnu.org 2024-03-18 15:33 ` ppalka at gcc dot gnu.org 2024-04-30 6:23 ` cvs-commit at gcc dot gnu.org 2024-04-30 7:31 ` nshead at gcc dot gnu.org 2024-05-06 11:51 ` adhemerval.zanella at linaro dot org 2024-05-06 16:35 ` pinskia at gcc dot gnu.org 2024-05-07 1:39 ` cvs-commit at gcc dot gnu.org 2024-05-24 14:17 ` cvs-commit at gcc dot gnu.org 2024-05-24 14:18 ` nshead at gcc dot gnu.org 2024-06-01 2:10 ` nshead 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-114275-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).