From: Martin Sebor <msebor@gmail.com>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Alias -Warray-bounds to -Warray-bounds=1
Date: Tue, 31 Jul 2018 20:58:00 -0000 [thread overview]
Message-ID: <9ed1681b-9c12-06ec-588a-99803d98232f@gmail.com> (raw)
In-Reply-To: <b1d4973f-7c26-d554-7496-d7def374592f@lauterbach.com>
I can't approve patches but this one seems to be in
the obvious category so I think it could be checked in
without formal approval.
It is however missing a couple of things: 1) a test case,
and 2) a reference to the bug it fixes in the ChangeLog
and in the test.
With that, if no one objects, I will commit the path for
you.
Martin
On 07/25/2018 08:04 AM, Franz Sirl wrote:
> Hi,
>
> as discussed with Martin, this patch consolidates -Warray-bounds into an
> alias of -Warray-bounds=1.
>
> Bootstrapped on x86_64-linux, no regressions.
>
> Please apply if it's OK.
>
> Franz.
>
>
>
next prev parent reply other threads:[~2018-07-31 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 14:05 Franz Sirl
2018-07-31 20:58 ` Martin Sebor [this message]
2018-08-03 18:27 ` Jeff Law
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=9ed1681b-9c12-06ec-588a-99803d98232f@gmail.com \
--to=msebor@gmail.com \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=gcc-patches@gcc.gnu.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).