https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99768
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |11.0
Blocks| |24639
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think the warning is correct - there is no valid initialization of a float
entity in 'tmp' (in fact GCC removed the initialization from 'v'). It might
be misleading but then what do you expect with invalid code?
We could, in theory, do another walk to find an initialization with strict
aliasing disabled and if we then find a candidate note that there are possible
initializations (we won't be able to prove they are definite inits) but
a violation of strict-aliasing might hide them. OTOH this would pop up a lot
and likely confuse people to use -fno-strict-aliasing to simply hide the
warning but not fix the missing initialization.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639
[Bug 24639] [meta-bug] bug to track all Wuninitialized issues
