public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Qing Zhao <qing.zhao@oracle.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: richard Biener <rguenther@suse.de>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: gcc-13/changes.html: Mention -fstrict-flex-arrays and its impact
Date: Tue, 17 Jan 2023 15:55:46 +0000	[thread overview]
Message-ID: <AB63F709-B20B-4F90-A6E1-672BEC78CF64@oracle.com> (raw)
In-Reply-To: <b6b3b29b-86a8-fe8b-754a-f2c958d0d0a6@pfeifer.com>

Thanks for the comment. 

I just committed the following:

From fc681f5412c421ff9609aea448310106d2570fd5 Mon Sep 17 00:00:00 2001
From: Qing Zhao <qing.zhao@oracle.com>
Date: Tue, 17 Jan 2023 15:52:15 +0000
Subject: [PATCH] gcc13/changes: update id 'flexible array' to
 'flexible-arrays' since ids must not contain white space

---
 htdocs/gcc-13/changes.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 08e36fb3..ca9cd2da 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -438,7 +438,7 @@ a work-in-progress.</p>
 <h2>Other significant improvements</h2>
 
 <!-- <h3 id="uninitialized">Eliminating uninitialized variables</h3> -->
-<h3 id="flexible array">Treating trailing arrays as flexible array members</h3>
+<h3 id="flexible-arrays">Treating trailing arrays as flexible array members</h3>
 
 <ul>
  <li>GCC can now control when to treat the trailing array of a structure as a
-- 
2.31.1


> On Jan 13, 2023, at 3:59 PM, Gerald Pfeifer <gerald@pfeifer.com> wrote:
> 
> 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


      reply	other threads:[~2023-01-17 15:55 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
2023-01-17 15:55   ` 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=AB63F709-B20B-4F90-A6E1-672BEC78CF64@oracle.com \
    --to=qing.zhao@oracle.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.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).