This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/70611] Compiling binutils with -flto -Wstack-usage fails.
- From: "manu at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 01 May 2016 19:47:13 +0000
- Subject: [Bug lto/70611] Compiling binutils with -flto -Wstack-usage fails.
- Auto-submitted: auto-generated
- References: <bug-70611-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70611
Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Last reconfirmed| |2016-05-01
CC| |manu at gcc dot gnu.org
Resolution|INVALID |---
Ever confirmed|0 |1
--- Comment #2 from Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> ---
(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.