public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Qing Zhao <qing.zhao@oracle.com>
To: rguenther@suse.de, joseph@codesourcery.com
Cc: gcc-patches@gcc.gnu.org, keescook@chromium.org,
	siddhesh@gcc.gnu.org, Qing Zhao <qing.zhao@oracle.com>
Subject: [V2][PATCH 0/1]Add a new warning option -Wstrict-flex-arrays
Date: Wed, 30 Nov 2022 14:25:55 +0000	[thread overview]
Message-ID: <20221130142556.3079865-1-qing.zhao@oracle.com> (raw)

Hi, this is the 2nd version for this patch.

Per our discussion, I made the following change compared to the first
version:

1. The level of -Warray-bounds will NOT control how a trailing array 
   is considered as a flex array member anymore. Only the level of  
   -fstrict-flex-arrays will control this;
2. Updating the documentation for -Warray-bounds by clarifying this
   change.
3. Updating the testing cases for such change.

I have bootstrapped and regression tested on both X86 and aarch64
without any issue.

Okay for committing?

thanks.

Qing




             reply	other threads:[~2022-11-30 14:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 14:25 Qing Zhao [this message]
2022-11-30 14:25 ` [V2][PATCH 1/1] Add " Qing Zhao
2022-12-01 16:42   ` Kees Cook
2022-12-01 17:04     ` Qing Zhao
2022-12-01 17:18       ` Kees Cook
2022-12-01 17:48         ` Qing Zhao
2022-12-01 19:45     ` Siddhesh Poyarekar
2022-12-01 22:27       ` Qing Zhao
2022-12-01 23:19         ` Kees Cook
2022-12-01 23:53           ` Siddhesh Poyarekar
2022-12-02  7:16       ` Richard Biener
2022-12-02  7:20         ` Richard Biener
2022-12-02 14:43           ` Qing Zhao
2022-12-05 15:16             ` Richard Biener
2022-12-05 15:20               ` Qing Zhao
2022-12-02 14:40         ` Qing Zhao

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=20221130142556.3079865-1-qing.zhao@oracle.com \
    --to=qing.zhao@oracle.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=keescook@chromium.org \
    --cc=rguenther@suse.de \
    --cc=siddhesh@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).