From: Hans-Peter Nilsson <hp@bitrange.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: gcc-patches@gcc.gnu.org, Richard Biener <rguenther@suse.de>
Subject: Re: [BUILDROBOT][PATCH] Fix mmix (unused variable)
Date: Sat, 19 Jul 2014 06:42:00 -0000 [thread overview]
Message-ID: <alpine.BSF.2.02.1407182023490.6913@arjuna.pair.com> (raw)
In-Reply-To: <20140718124444.GU21544@lug-owl.de>
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?
brgds, H-P
next prev parent reply other threads:[~2014-07-19 0:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 5:04 Jan-Benedict Glaw
2014-07-18 8:08 ` Hans-Peter Nilsson
2014-07-18 13:11 ` Jan-Benedict Glaw
2014-07-19 6:42 ` Hans-Peter Nilsson [this message]
2014-07-19 17:27 ` Jan-Benedict Glaw
2014-07-22 13:01 ` Richard Biener
2014-07-22 20:49 ` werror fallout for cross-builds (was: Re: [BUILDROBOT][PATCH] Fix mmix (unused variable)) Hans-Peter Nilsson
2014-07-22 22:12 ` werror fallout for cross-builds Andreas Schwab
2014-07-23 0:09 ` werror fallout for cross-builds (was: Re: [BUILDROBOT][PATCH] Fix mmix (unused variable)) Mike Stump
2014-07-23 2:54 ` Hans-Peter Nilsson
2014-07-23 8:06 ` Mike Stump
2014-07-24 11:13 ` Maciej W. Rozycki
2014-07-24 0:42 ` Jan-Benedict Glaw
2014-07-24 20:56 ` Hans-Peter Nilsson
2014-07-25 9:58 ` Jan-Benedict Glaw
2014-07-25 16:51 ` Hans-Peter Nilsson
2014-07-26 17:33 ` Hans-Peter Nilsson
2014-08-22 11:55 ` Jan-Benedict Glaw
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.BSF.2.02.1407182023490.6913@arjuna.pair.com \
--to=hp@bitrange.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jbglaw@lug-owl.de \
--cc=rguenther@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).