: diagnostic, lto
Severity: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: dobonachea at lbl dot gov
CC: marxin at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-pc-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83954
--- Comment #2 from Dan Bonachea ---
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 gene
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83954
--- Comment #5 from Dan Bonachea ---
(In reply to Martin Liška from comment #4)
> > 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)
>
> Ye
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83954
--- Comment #8 from Dan Bonachea ---
(In reply to Jan Hubicka from comment #7)
> This should silence the warning.
> Index: lto-symtab.c
> ===
> --- lto-symtab.c(revision 2570