https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95516
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2020-06-04
Status|UNCONFIRMED |NEW
--- Comment #1 from Iain Sandoe <iains at gcc dot gnu.org> ---
Thanks for the report.
this is a kinda tricky situation;
I have also seen this occur (in larger test cases)
1) the coro.gro variable is an internal one to the compiler (it is also marked
as such). So the user can't "fix" the problem...
2) coro.gro is always initialised unconditionally in the same fragment of code
that creates it.
so it seems a false positive (actually, the example code posted here does not
fail for me on either 10.x or master) - however, as noted, I have seen this
occur.
- so this is a problem with the subsequent diagnostics processing or
optimisation.
