From: Alan Modra <amodra@gmail.com>
To: tbsaunde+binutils@tbsaunde.org
Cc: binutils@sourceware.org
Subject: Re: [PATCH] move the computation of C++ warning flags to bfd/warning.m4
Date: Mon, 04 Apr 2016 00:38:00 -0000 [thread overview]
Message-ID: <20160404003753.GP27246@bubble.grove.modra.org> (raw)
In-Reply-To: <1459704127-16182-1-git-send-email-tbsaunde+binutils@tbsaunde.org>
On Sun, Apr 03, 2016 at 01:22:07PM -0400, tbsaunde+binutils@tbsaunde.org wrote:
> There isn't anything specific to gold about this code, so it would seem to make
> sense to compute C and C++ warning flags in the same place. This also means
> that anything else that wants C++ warning flags won't have to roll there own.
I think I prefer things the way they are, but in any case will defer
to Cary's opinion on whether this patch should be accepted.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2016-04-04 0:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-03 17:17 tbsaunde+binutils
2016-04-04 0:38 ` Alan Modra [this message]
2016-04-04 9:42 ` Pedro Alves
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=20160404003753.GP27246@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=tbsaunde+binutils@tbsaunde.org \
/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).