https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83954
--- Comment #2 from Dan Bonachea <dobonachea at lbl dot gov> --- Thanks Mr. Liška! If possible it would be useful for our project to know whether this defect is solely a spurious warning, or whether it could affect analysis in a way that might result in incorrect code generation on affected compiler versions (as suggested by the warning text). 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)
