https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115908
Arsen Arsenović <arsen at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |arsen at gcc dot gnu.org
Last reconfirmed| |2024-07-30
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #3 from Arsen Arsenović <arsen at gcc dot gnu.org> ---
the sequencing rule is a bit annoying here, we determine the result of the
initial coroutine call only after the first suspend (which might not be the
initial suspend), but I think we can do this correctly anyway. currently, we
use an intermediary variable called _Coro_gro in the case you showed, hence the
difference in behavior. confirmed
