From: Qing Zhao <QING.ZHAO@ORACLE.COM>
To: David Malcolm <dmalcolm@redhat.com>
Cc: Richard Sandiford <richard.sandiford@arm.com>,
Qing Zhao via Gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Committed [Version 3][PATCH][gcc][PR94230]provide an option to change the size limitation for -Wmisleading-indent
Date: Wed, 6 May 2020 13:40:04 -0500 [thread overview]
Message-ID: <AA0D3697-4866-4194-A200-2FE6F14AAA66@ORACLE.COM> (raw)
In-Reply-To: <a407e6691ad5d7235c79d9c5eb251ddd401036f9.camel@redhat.com>
FYI.
> On Apr 23, 2020, at 5:13 PM, David Malcolm <dmalcolm@redhat.com> wrote:
>
> May need updating to match the hint message.
>
> [...]
>
> This is OK for stage 1 with those nits fixed.
I committed the updated patch with all the suggestions today to gcc11 stage1 as:
https://gcc.gnu.org/g:530b44094354758d0dea5374188caa6863647114 <https://gcc.gnu.org/g:530b44094354758d0dea5374188caa6863647114>
Thanks.
Qing
>
> There was talk earlier in the thread about fixing this in GCC 10.
>
> Richi/Jakub: is this OK for stage 4? Although it adds a new command-
> line option, it's a workaround for a regression introduced in GCC 6 and
> should be low risk.
>
> Thanks
> Dave
>
prev parent reply other threads:[~2020-05-06 18:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 19:55 [PATCH][gcc][PR94230]provide " Qing Zhao
2020-04-08 19:39 ` PING " Qing Zhao
2020-04-15 20:30 ` Fwd: " Qing Zhao
2020-04-21 14:04 ` Richard Sandiford
2020-04-21 15:21 ` David Malcolm
2020-04-21 18:46 ` Richard Sandiford
2020-04-22 14:22 ` Qing Zhao
2020-04-23 14:41 ` [Version 2][PATCH][gcc][PR94230]provide " Qing Zhao
2020-04-23 18:27 ` Richard Sandiford
2020-04-23 19:52 ` Qing Zhao
2020-04-23 21:05 ` [Version 3][PATCH][gcc][PR94230]provide " Qing Zhao
2020-04-23 22:13 ` David Malcolm
2020-04-24 22:22 ` [Version 4][PATCH][gcc][PR94230]provide " Qing Zhao
2020-04-24 22:36 ` David Malcolm
2020-04-27 14:23 ` Qing Zhao
2020-05-06 18:40 ` Qing Zhao [this message]
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=AA0D3697-4866-4194-A200-2FE6F14AAA66@ORACLE.COM \
--to=qing.zhao@oracle.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.com \
/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).