https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70611
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (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 compiling. stack usage is one of these > > warnings. > > How can a user know which warnings are those? GCC should disable on its own > those warnings that cannot be handled by LTO (or emit a clear error that the > warning is not valid with LTO). Same with invalid optimization options and > attributes. > > If LTO is ever going to be usable by anyone who is not a GCC developer, it > needs to be usable without knowing the internals of the compiler. 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 those options ...
