public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114275] using std::thread within a templated function in a module fails to compile Date: Fri, 08 Mar 2024 15:09:34 +0000 [thread overview] Message-ID: <bug-114275-4-JXz2hTwbA1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114275-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114275 --- Comment #3 from Patrick Palka <ppalka at gcc dot gnu.org> --- PR105320 seems similar. Another maybe related testcase: $ cat testcase.C export module M; template<class> struct A { template<class> friend struct B; }; A<int> a; template<class> struct B { }; $ cat testcase.C | g++ -fmodules-ts -x c++ - <stdin>:6:27: error: cannot declare ‘struct B< <template-parameter-1-1> >’ in a different module <stdin>:3:34: note: declared here <stdin>:1:8: warning: not writing module ‘M’ due to errors
next prev parent reply other threads:[~2024-03-08 15:09 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-08 2:04 [Bug c++/114275] New: " michael.kenzel at gmail dot com 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 [this message] 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-JXz2hTwbA1@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).