https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77395
--- Comment #3 from Johannes S. Mueller-Roemer ---
(In reply to Daniel Krügler from comment #1)
> I think a better test-case is the following one, which does not depend on
> tuple at all:
>
> //#
> #include
>
>
: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: j.s.mueller-roemer at gmx dot net
Target Milestone: ---
Created attachment 39504
--> https://gcc.gnu.org/bugzilla/attachment.cgi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59474
Johannes S. Mueller-Roemer changed:
What|Removed |Added
CC||j.s.mueller-roemer at gmx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67436
--- Comment #3 from Johannes S. Mueller-Roemer ---
The following workaround seems to work as well:
int main(int, char**)
{
thread_local int foo;
[=foo] (auto bar) {
foo += bar;
}(1u);
return 0;
}
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: j.s.mueller-roemer at gmx dot net
Target Milestone: ---
I encountered an error with a missing __tls_init after using a thread_local
variable within a generic lambda. I was able to work
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67436
--- Comment #2 from Johannes S. Mueller-Roemer ---
(In reply to Jonathan Wakely from comment #1)
> (In reply to Johannes S. Mueller-Roemer from comment #0)
> > I encountered an error with a missing __tls_init after using a thread_local
> >
