public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Qing Zhao <qing.zhao@oracle.com>
To: jason@redhat.com, richard.guenther@gmail.com, josmyers@redhat.com
Cc: uecker@tugraz.at, siddhesh@gotplt.org, keescook@chromium.org,
	gcc-patches@gcc.gnu.org, Qing Zhao <qing.zhao@oracle.com>
Subject: [PATCH v2 0/3] Allow flexible array members in unions and alone in structures [PR53548]
Date: Thu, 25 Apr 2024 14:06:45 +0000	[thread overview]
Message-ID: <20240425140648.1407274-1-qing.zhao@oracle.com> (raw)

Hi,

This is the 2nd version for 
Allow flexible array members in unions and alone in structures [PR53548]

(for your reference, the 1st version is at:
https://gcc.gnu.org/pipermail/gcc-patches/2024-April/649737.html)

compared to the 1st version, the major difference are:

A. C FE updates based on Joseph's comments:

   documentation changes;

   testing case changes; 
   * added testing cases for -pedantic-errors;
   * renamed the testing cases to accurately reflect the covered tests;
   * added unnamed bit-fields along with FAM;
   * move the testing cases to c-c++-common;

B. Merge the 4th patch (old testing adjustment) to the 2nd patch in order to 
   avoid testing regressions if individual patch is tested separately. 

Approval status:

   C FE and documentation changes have been approved for GCC15 with the above update A. 
   (Patch 1 and Patch 3 have been approved, the C FE part of Patch 2
    has been approved). 

Review needed:

   C++ FE changes (in Patch 2);
   Middle-end changes (in Patch 2);

The patch set includes:
 1. Documentation change.
    Allow flexible array members in unions and alone in structures
    [PR53548]
 2. C and C++ FE changes to support flexible array members in unions and
   alone in structures.
    Adjust testcases for flexible array member in union and alone in
   structure extension.
 3. Add testing cases for flexible array members in unions and alone in
   structures.

bootstrapped and regression tested on both x86 and aarch64, no issue.

Okay for GCC15?

thanks.

Qing

             reply	other threads:[~2024-04-25 14:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 14:06 Qing Zhao [this message]
2024-04-25 14:06 ` [PATCH v2 1/3] " Qing Zhao
2024-04-25 14:06 ` [PATCH v2 2/3] C and C++ FE changes Qing Zhao
2024-04-25 14:06 ` [PATCH v2 3/3] Add testing cases for flexible array members in unions and alone in structures Qing Zhao
2024-04-25 14:13   ` Siddhesh Poyarekar
2024-04-25 14:21     ` 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=20240425140648.1407274-1-qing.zhao@oracle.com \
    --to=qing.zhao@oracle.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=josmyers@redhat.com \
    --cc=keescook@chromium.org \
    --cc=richard.guenther@gmail.com \
    --cc=siddhesh@gotplt.org \
    --cc=uecker@tugraz.at \
    /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).