https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79627
Marek Polacek changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79627
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79627
--- Comment #4 from Martin Liška ---
(In reply to Arseny Solokha from comment #3)
> It is fixed for gcc 10, probably by
> g:00a49cd840f60774b0e9e0109fb10559bc9a9194.
Yes, it's fixed with this commit.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79627
Arseny Solokha changed:
What|Removed |Added
CC||asolokha at gmx dot com
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79627
Volker Reichelt changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79627
--- Comment #2 from Andrew Pinski ---
*** Bug 79656 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79627
--- Comment #1 from Jakub Jelinek ---
This is nasty, all we have is a SAVE_EXPR that is evaluated both outside of the
lambda and inside of it, so ideally we'd capture a temporary assigned that
SAVE_EXPR and use it inside of the lambda. But no