This is the mail archive of the
mailing list for the GCC project.
Re: [BUILDROBOT][PATCH] Fix mmix (unused variable)
- From: Richard Biener <rguenther at suse dot de>
- To: Hans-Peter Nilsson <hp at bitrange dot com>
- Cc: Jan-Benedict Glaw <jbglaw at lug-owl dot de>, gcc-patches at gcc dot gnu dot org
- Date: Tue, 22 Jul 2014 14:57:42 +0200 (CEST)
- Subject: Re: [BUILDROBOT][PATCH] Fix mmix (unused variable)
- Authentication-results: sourceware.org; auth=none
- References: <20140718020136 dot GT21544 at lug-owl dot de> <alpine dot BSF dot 2 dot 02 dot 1407180256200 dot 66146 at arjuna dot pair dot com> <20140718124444 dot GU21544 at lug-owl dot de> <alpine dot BSF dot 2 dot 02 dot 1407182023490 dot 6913 at arjuna dot pair dot com>
On Fri, 18 Jul 2014, Hans-Peter Nilsson wrote:
> On Fri, 18 Jul 2014, Jan-Benedict Glaw wrote:
> > This was a build using GCC's ./contrib/config-list.mk to do the build.
> > It passes --enable-werror-always to top-level `configure', this is
> > where the -Werror comes from.
> Aha. Looks like it's of more use than theoretical pain; sounds
> like this should (effectively) be the default for *non-releases*
> when cross-compiling, with the possibility to override
> per-target. Agreement? Anyone against? 1/2 :)
> It should be per-target because there *may* be port-specific
> constructs warned about by buggy previous-but-not-ancient
> gcc-versions, where working around the warnings would cause
> unwanted obfuscation. (IIRC gdb does something like this.)
> Is that the reason it's not the default, that there are such
> constructs in the non-port-specific parts? But then that would
> have already been noticed through use of the config-list.mk, no?
The reason it's not the default is because the warnings are coming
from the host compiler which may be fairly old or even broken.
If we want it to make the default the we should restrict it
based on the host compiler (version).