public inbox for
 help / color / mirror / Atom feed
From: Qing Zhao <>
	Qing Zhao <>
Subject: [PATCH 0/2] [GCC13][Patch][V5][PATCH 0/2] Add a new option -fstrict-flex-arrays[=n] and attribute strict_flex_array(n) and use it in PR101836
Date: Tue,  4 Oct 2022 15:21:51 +0000	[thread overview]
Message-ID: <> (raw)

This is the 5th version of the patch set.
Compare to the 4th version, the following are the major change:(Address
Martin's comments).

  1. change the name of the attribute from "strict_flex_arrays" to
  2. update document to update all mentions of flexible array member
with additional qualification "for the purposes of accessing the
elements of such array".

Compare to the 3rd version, the following are the major change:

1. delete all the warnings for the confliction between -std and
-fstrict-flex-arrays per our discussion.
2. delete all the related testing cases for these warnings.
3. update all the wording changes, and documentation format changes
recommanded by Joseph.
I have bootstrapped and regression tested on both aarch64 and x86, no issues.

The above changes are all in documentation and FEs.

Since the Middle end change has been Okayed by Bichard in the V3 of the
patch review. So, Joseph, could you please take a look at the FE  and
doc changes and let me know whether they are good to commit?

thanks a lot.


Qing Zhao (2):
  Add a new option -fstrict-flex-arrays[=n] and new attribute
  Use array_at_struct_end_p in __builtin_object_size [PR101836]

             reply	other threads:[~2022-10-04 15:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 15:21 Qing Zhao [this message]
2022-10-04 15:21 ` [GCC13][Patch][V5][PATCH 1/2] Add a new option -fstrict-flex-arrays[=n] and new attribute strict_flex_array Qing Zhao
2022-10-04 17:37   ` Joseph Myers
2022-10-05 14:04     ` Qing Zhao
2022-10-04 15:21 ` [GCC13][Patch][V5][PATCH 2/2] Use array_at_struct_end_p in __builtin_object_size [PR101836] 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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).