https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117600
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Richard Earnshaw from comment #6)
> libgcc is always built with the target compiler. --disable-werror is
> intended to allow compliers other than the one being built to work when they
> generate warnings based on different algorithms. It would be inappropriate
> to cross-link the two issues under the same configure flag.
It is also intended when using some more unusual CXXFLAGS or configurations.
E.g. when trying to build the compiler as -Os or -O3, different (perhaps false
positive) -Wmaybe-uninitialized warnings etc. might be emitted.
For what is compiled into cc1 etc., for -O2 we make sure no warnings build the
build, but if people do something unusual/weird, they should be able to compile
despite some false positive warnings from time to time.
