public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Kees Cook <keescook@chromium.org>, Qing Zhao <qing.zhao@oracle.com>
Cc: rguenther@suse.de, joseph@codesourcery.com,
	gcc-patches@gcc.gnu.org, siddhesh@gcc.gnu.org
Subject: Re: [V2][PATCH 1/1] Add a new warning option -Wstrict-flex-arrays.
Date: Thu, 1 Dec 2022 14:45:47 -0500	[thread overview]
Message-ID: <898dfeed-f392-fb86-7fbd-f99d335c7a64@gotplt.org> (raw)
In-Reply-To: <202212010840.C963E72661@keescook>

On 2022-12-01 11:42, Kees Cook wrote:
> On Wed, Nov 30, 2022 at 02:25:56PM +0000, Qing Zhao wrote:
>> '-Wstrict-flex-arrays'
>>       Warn about inproper usages of flexible array members according to
>>       the LEVEL of the 'strict_flex_array (LEVEL)' attribute attached to
>>       the trailing array field of a structure if it's available,
>>       otherwise according to the LEVEL of the option
>>       '-fstrict-flex-arrays=LEVEL'.
>>
>>       This option is effective only when LEVEL is bigger than 0.
>>       Otherwise, it will be ignored with a warning.
>>
>>       when LEVEL=1, warnings will be issued for a trailing array
>>       reference of a structure that have 2 or more elements if the
>>       trailing array is referenced as a flexible array member.
>>
>>       when LEVEL=2, in addition to LEVEL=1, additional warnings will be
>>       issued for a trailing one-element array reference of a structure if
>>       the array is referenced as a flexible array member.
>>
>>       when LEVEL=3, in addition to LEVEL=2, additional warnings will be
>>       issued for a trailing zero-length array reference of a structure if
>>       the array is referenced as a flexible array member.
>>
>> At the same time, -Warray-bounds is updated:
> 
> Why is there both -Wstrict-flex-arrays and -Warray-bounds? I thought
> only the latter was going to exist?

Oh my understanding of the consensus was to move flex array related 
diagnosis from -Warray-bounds to -Wstring-flex-arrays as Qing has done. 
If only the former exists then instead of removing the flex array 
related statement in the documentation as Richard suggested, we need to 
enhance it to say that behaviour of -Warray-bounds will depend on 
-fstrict-flex-arrays.

-Warray-bounds does diagnosis beyond just flexible arrays, in case 
that's the confusion.

Sid

  parent reply	other threads:[~2022-12-01 19:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 14:25 [V2][PATCH 0/1]Add " Qing Zhao
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 [this message]
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
2022-12-06 16:14 [V3][PATCH 0/2]Update -Warray-bounds with -fstrict-flex-arrays Qing Zhao
2022-12-06 16:14 ` [V2][PATCH 1/1] Add a new warning option -Wstrict-flex-arrays Qing Zhao
2022-12-06 16:16   ` 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=898dfeed-f392-fb86-7fbd-f99d335c7a64@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=keescook@chromium.org \
    --cc=qing.zhao@oracle.com \
    --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).