From: Qing Zhao <qing.zhao@oracle.com>
To: Joseph Myers <joseph@codesourcery.com>,
Richard Biener <rguenther@suse.de>
Cc: "siddhesh@gotplt.org" <siddhesh@gotplt.org>,
"keescook@chromium.org" <keescook@chromium.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [v3][PATCH 0/2] Handle component_ref to a structure/union field including FAM for builtin_object_size
Date: Fri, 17 Feb 2023 13:57:33 +0000 [thread overview]
Message-ID: <B50E929C-08C3-478F-BCEE-954539C1AC9C@oracle.com> (raw)
In-Reply-To: <20230211005013.789161-1-qing.zhao@oracle.com>
Ping…
Qing
> On Feb 10, 2023, at 7:50 PM, Qing Zhao <qing.zhao@oracle.com> wrote:
>
> These are the 3rd version of the patches for PR101832, to fix
> builtin_object_size to correctly handle component_ref to a
> structure/union field that includes a flexible array member.
>
> also includes a documentation update for the GCC extension on embedding
> a structure/union with flexible array member into another structure.
> which includes a fix to PR77650.
>
> compared to the 2nd version of the patch, the major changes are:
> 1. only include C99 flexible array member to this extension, trailing [0], [1]
> and [4] are all excluded.
> 2. for the new bit type_include_flexarray in tree_type_common, print it
> and also stream in/out it.
> 3. update testing cases.
> 4. more clarification on the documentation. warnings for deprecating the
> case when the structure with C99 FAM is embedded in the middle of
> another structure.
> 5. add a new warning option -Wgnu-variable-sized-type-not-at-end for
> identifing all such cases.
>
> bootstrapped and regression tested on aarch64 and x86.
>
> Okay for commit?
>
> thanks.
>
> Qing
>
prev parent reply other threads:[~2023-02-17 13:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 0:50 Qing Zhao
2023-02-11 0:50 ` [v3][PATCH 1/2] Handle component_ref to a structre/union field including C99 FAM [PR101832] Qing Zhao
2023-02-17 13:57 ` Qing Zhao
2023-02-23 14:12 ` Fwd: " Qing Zhao
2023-02-11 0:50 ` [v3][PATCH 2/2] Update documentation to clarify a GCC extension (PR77650) Qing Zhao
2023-02-17 13:58 ` Qing Zhao
2023-02-23 14:14 ` Fwd: " Qing Zhao
2023-02-23 21:24 ` Joseph Myers
2023-02-23 22:04 ` Qing Zhao
2023-02-23 22:30 ` Qing Zhao
2023-02-24 0:56 ` Joseph Myers
2023-02-24 13:50 ` Qing Zhao
2023-02-17 13:57 ` 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=B50E929C-08C3-478F-BCEE-954539C1AC9C@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@gotplt.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).