public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia 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 02:19:24 +0000	[thread overview]
Message-ID: <bug-114275-4-ghBBv3bJkN@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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |rejects-valid

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
In file included from
/home/apinski/upstream-gcc-match/include/c++/14.0.1/bits/std_thread.h:39,
                 from
/home/apinski/upstream-gcc-match/include/c++/14.0.1/stop_token:40,
                 from
/home/apinski/upstream-gcc-match/include/c++/14.0.1/thread:42,
                 from A.ixx:4,
of module A, imported at main.cpp:2:
/home/apinski/upstream-gcc-match/include/c++/14.0.1/tuple: In instantiation of
‘struct std::_Tuple_impl@A<0, fun@A<int>(int&&)::<lambda()> >’:
/home/apinski/upstream-gcc-match/include/c++/14.0.1/tuple:834:11:   required
from ‘class std::tuple@A<fun@A<int>(int&&)::<lambda()> >’
  834 |     class tuple : public _Tuple_impl<0, _Elements...>
      |           ^~~~~
/home/apinski/upstream-gcc-match/include/c++/14.0.1/bits/std_thread.h:280:9:  
required from ‘struct
std::thread@A::_Invoker<std::tuple@A<fun@A<int>(int&&)::<lambda()> > >’
  280 |         _Tuple _M_t;
      |                ^~~~
/home/apinski/upstream-gcc-match/include/c++/14.0.1/bits/std_thread.h:236:13:  
required from ‘struct
std::thread@A::_State_impl<std::thread@A::_Invoker<std::tuple@A<fun@A<int>(int&&)::<lambda()>
> > >’
  236 |         _Callable               _M_func;
      |                                 ^~~~~~~
/home/apinski/upstream-gcc-match/include/c++/14.0.1/bits/std_thread.h:164:29:  
required from ‘std::thread@A::thread(_Callable&&, _Args&& ...) [with _Callable
= fun@A<int>(int&&)::<lambda()>; _Args = {}; <template-parameter-1-3> = void]’
  164 |         _M_start_thread(_State_ptr(new _State_impl<_Wrapper>(
      |                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~
  165 |               std::forward<_Callable>(__f),
std::forward<_Args>(__args)...)),
      |              
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A.ixx:10:8:   required from ‘void fun@A(auto:38&&) [with auto:38 = int]’
   10 |                 std::thread([]{}).join();
      |                      ^~~~~~~~~~~~
main.cpp:6:6:   required from here
    6 |                 fun(42);
      |                 ~~~^~~~
/home/apinski/upstream-gcc-match/include/c++/14.0.1/tuple:551:51: error:
conflicting declaration of template ‘template<long unsigned int <anonymous>,
class ...> struct std::_Tuple_impl’
  551 |       template<size_t, typename...> friend struct _Tuple_impl;
      |                                                   ^~~~~~~~~~~

  reply	other threads:[~2024-03-08  2:19 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 ` pinskia at gcc dot gnu.org [this message]
2024-03-08  3:15 ` [Bug c++/114275] " 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-ghBBv3bJkN@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: link
Be 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).