https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83954
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> --- > Assuming it's the latter, can anyone suggest any non-intrusive workarounds? > (aside from the obvious "big hammers" of -fno-lto or -fno-strict-aliasing) Yes, the warning should not produce bogus warnings. Proper solution is not to break strict aliasing. Note that it can help optimization to make more aggressive optimizations.
