From: Gerald Pfeifer <gerald@pfeifer.com>
To: Qing Zhao <qing.zhao@oracle.com>
Cc: richard Biener <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Subject: Re: gcc-13/changes.html: Mention -fstrict-flex-arrays and its impact
Date: Fri, 13 Jan 2023 21:59:48 +0100 (CET) [thread overview]
Message-ID: <b6b3b29b-86a8-fe8b-754a-f2c958d0d0a6@pfeifer.com> (raw)
In-Reply-To: <FF9C7E0B-5DF6-4FC2-B3C2-29F3CBCBE147@oracle.com>
On Tue, 20 Dec 2022, Qing Zhao via Gcc-patches wrote:
> +<h3 id="flexible array">Treating trailing arrays as flexible array members</h3>
Please note that ids must not contain white space.
Would you mind following up making this "flexiblearray" or similiar?
Thank you,
Gerald
next prev parent reply other threads:[~2023-01-13 21:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 16:16 Qing Zhao
2022-12-21 7:12 ` Richard Biener
2022-12-21 14:46 ` Qing Zhao
2022-12-22 7:09 ` Richard Biener
2022-12-22 16:41 ` Qing Zhao
2023-01-09 7:11 ` Richard Biener
2023-01-09 15:07 ` Qing Zhao
2023-01-10 8:06 ` Richard Biener
2023-01-10 13:25 ` Qing Zhao
2023-01-13 20:59 ` Gerald Pfeifer [this message]
2023-01-17 15:55 ` 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=b6b3b29b-86a8-fe8b-754a-f2c958d0d0a6@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=qing.zhao@oracle.com \
--cc=rguenther@suse.de \
/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).