public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/53548] allow flexible array members in unions like zero-length arrays
Date: Mon, 06 May 2024 18:36:35 +0000	[thread overview]
Message-ID: <bug-53548-4-X8wKG8s0oE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53548-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53548

--- Comment #13 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Qing Zhao <qinzhao@gcc.gnu.org>:

https://gcc.gnu.org/g:93f6a47583f3fa8a1b66856ecb19ec28f26b2ba4

commit r15-210-g93f6a47583f3fa8a1b66856ecb19ec28f26b2ba4
Author: Qing Zhao <qing.zhao@oracle.com>
Date:   Mon May 6 16:27:09 2024 +0000

    Add testing cases for flexible array members in unions and alone in
structures.

    PR c/53548

    gcc/testsuite/ChangeLog:

            PR c/53548
            * c-c++-common/fam-in-union-alone-in-struct-1.c: New testcase.
            * c-c++-common/fam-in-union-alone-in-struct-2.c: New testcase.
            * c-c++-common/fam-in-union-alone-in-struct-3.c: New testcase.

  parent reply	other threads:[~2024-05-06 18:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-01  2:13 [Bug c/53548] New: " vapier at gentoo dot org
2012-06-04  0:50 ` [Bug c/53548] " carlos_odonell at mentor dot com
2024-03-08 20:41 ` kees at outflux dot net
2024-03-08 20:42 ` kees at outflux dot net
2024-03-08 20:50 ` kees at outflux dot net
2024-03-13 19:34 ` qinzhao at gcc dot gnu.org
2024-04-08 18:20 ` qinzhao at gcc dot gnu.org
2024-05-06 18:36 ` cvs-commit at gcc dot gnu.org
2024-05-06 18:36 ` cvs-commit at gcc dot gnu.org
2024-05-06 18:36 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-06 18:36 ` cvs-commit at gcc dot gnu.org
2024-05-06 18:40 ` qinzhao at gcc dot gnu.org

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=bug-53548-4-X8wKG8s0oE@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).