https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70611
Sam James changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70611
--- Comment #8 from Sam James ---
(In reply to Manuel López-Ibáñez from comment #4)
AFAIK, it's "just" the generic late-optimisation warnings issue in general, so
the warning isn't broken with LTO, it's just more likely to have be bogus
there.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70611
--- Comment #7 from Mark Wielaard ---
(In reply to Mark Wielaard from comment #6)
> Sorry, commented on the wrong bug, the above was meant for bug #93865
Groan, I seem very confused today. That comment was fine. It was me who got
confused becaus
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70611
--- Comment #6 from Mark Wielaard ---
(In reply to Mark Wielaard from comment #5)
> This is also one of the issues that prevent elfutils to build with LTO.
> The workaround is to compile with -Wno-error=stack-usage= added to CFLAGS:
> https://sou
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70611
Mark Wielaard changed:
What|Removed |Added
CC||mark at gcc dot gnu.org
--- Comment #5 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70611
--- Comment #4 from Manuel López-Ibáñez ---
(In reply to Andrew Pinski from comment #3)
> There is no internals of GCC here. Rather the user specified all warnings
> at link time. If the user did not want that then they did not need to
> supply
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70611
--- Comment #3 from Andrew Pinski ---
(In reply to Manuel López-Ibáñez from comment #2)
> (In reply to Andrew Pinski from comment #1)
> > If you are going to be using lto you need to disable warnings as some
> > warnings don't happen until end of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70611
Manuel López-Ibáñez changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70611
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
