This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/55496] False positive -Werror=uninitialized breaks profiledbootstrap and bootstrap-lto
- From: "egallager at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 30 Dec 2017 03:01:38 +0000
- Subject: [Bug bootstrap/55496] False positive -Werror=uninitialized breaks profiledbootstrap and bootstrap-lto
- Auto-submitted: auto-generated
- References: <bug-55496-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55496
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2017-12-30
Ever confirmed|0 |1
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #4)
> There are a ton of warnings in profiledbootstrap, including -Wuninitialized
> (see the full list below for an x86_64 GCC 7.0 configured with
> --enable-languages=ada,all,c,c++,fortran,go,objc,obj-c++
> -with-build-config=bootstrap-lto --disable-werror). My understanding is
> that it's not really expected to work without --disable-werror.
I think it'd still be worth fixing them, though, so I'm taking this as
confirmation.