From: Richard Biener <rguenther@suse.de>
To: Kees Cook <keescook@chromium.org>
Cc: Qing Zhao <qing.zhao@oracle.com>,
"Joseph@codesourcery.com" <Joseph@codesourcery.com>,
jakub Jelinek <jakub@redhat.com>,
gcc Patches <gcc-patches@gcc.gnu.org>,
Nathan Sidwell <Nathan@acm.org>, martin Sebor <msebor@gmail.com>
Subject: Re: [[GCC13][Patch][V3] 1/2] Add a new option -fstrict-flex-array[=n] and new attribute strict_flex_array
Date: Thu, 1 Sep 2022 06:11:34 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2209010611240.14286@jbgna.fhfr.qr> (raw)
In-Reply-To: <202208311517.68258F82DF@keescook>
On Wed, 31 Aug 2022, Kees Cook wrote:
> On Wed, Aug 31, 2022 at 08:35:12PM +0000, Qing Zhao wrote:
> > One of the major purposes of the new option -fstrict-flex-array is to encourage standard conforming programming style.
> >
> > So, it might be reasonable to treat -fstrict-flex-array similar as -pedantic (but only for flexible array members)?
> > If so, then issuing warnings when the standard doesn?t support is reasonable and desirable.
>
> I guess the point is that "-std=c89 -fstrict-flex-arrays=3" leaves "[]"
> available for use still? I think this doesn't matter. If someone wants
> it to be really strict, they'd just add -Wpedantic.
Yes, I think that makes sense.
Richard.
next prev parent reply other threads:[~2022-09-01 6:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 14:40 Qing Zhao
2022-08-17 14:40 ` [[GCC13][Patch][V3] 2/2] Use array_at_struct_end_p in __builtin_object_size [PR101836] Qing Zhao
2022-08-26 8:49 ` Richard Biener
2022-08-26 13:37 ` Qing Zhao
2022-08-26 8:48 ` [[GCC13][Patch][V3] 1/2] Add a new option -fstrict-flex-array[=n] and new attribute strict_flex_array Richard Biener
2022-08-26 13:47 ` Qing Zhao
2022-08-29 8:04 ` Richard Biener
2022-08-30 20:30 ` Fwd: " Qing Zhao
2022-08-30 20:30 ` Qing Zhao
2022-08-30 22:53 ` Joseph Myers
2022-08-31 14:00 ` Qing Zhao
2022-08-31 17:21 ` Joseph Myers
2022-08-31 17:21 ` Joseph Myers
2022-08-31 18:55 ` Qing Zhao
2022-08-31 19:24 ` Qing Zhao
2022-08-31 19:29 ` Joseph Myers
2022-08-31 19:29 ` Joseph Myers
2022-08-31 19:47 ` Qing Zhao
2022-08-31 19:52 ` Joseph Myers
2022-08-31 20:06 ` Qing Zhao
2022-08-31 20:09 ` Joseph Myers
2022-08-31 20:16 ` Qing Zhao
2022-08-31 20:35 ` Qing Zhao
2022-08-31 22:23 ` Kees Cook
2022-09-01 6:11 ` Richard Biener [this message]
2022-09-04 14:17 ` Qing Zhao
2022-08-31 22:17 ` Kees Cook
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=nycvar.YFH.7.77.849.2209010611240.14286@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=Joseph@codesourcery.com \
--cc=Nathan@acm.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=keescook@chromium.org \
--cc=msebor@gmail.com \
--cc=qing.zhao@oracle.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).