From: Joseph Myers <joseph@codesourcery.com>
To: Qing Zhao <qing.zhao@oracle.com>
Cc: Richard Biener <rguenther@suse.de>,
Siddhesh Poyarekar <siddhesh@gotplt.org>,
Kees Cook <keescook@chromium.org>,
Gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Fwd: [v3][PATCH 2/2] Update documentation to clarify a GCC extension (PR77650)
Date: Thu, 23 Feb 2023 21:24:09 +0000 [thread overview]
Message-ID: <68c735b-90cc-14ef-be83-db1b754ad0f4@codesourcery.com> (raw)
In-Reply-To: <89D4C326-54FD-4403-8E54-6CE5B21AA411@oracle.com>
On Thu, 23 Feb 2023, Qing Zhao via Gcc-patches wrote:
> +@item
> +The structure with a C99 flexible array member is the field of
> +another union, for example:
> +
> +@smallexample
> +struct flex1 @{ int length1; char data1[]; @}
> +struct flex2 @{ int length2; char data2[]; @}
> +
> +union out_flex @{ struct flex1 flex_data1; struct flex2 flex_data2; @}
I don't think this is an extension; structures with flexible array members
are OK in unions in standard C.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-02-23 21:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 0:50 [v3][PATCH 0/2] Handle component_ref to a structure/union field including FAM for builtin_object_size 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 [this message]
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 ` [v3][PATCH 0/2] Handle component_ref to a structure/union field including FAM for builtin_object_size 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=68c735b-90cc-14ef-be83-db1b754ad0f4@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=keescook@chromium.org \
--cc=qing.zhao@oracle.com \
--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).