public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/100124] Why is "flexible array member '...' in an otherwise empty '...'" an issue?
Date: Sat, 17 Apr 2021 00:51:24 +0000 [thread overview]
Message-ID: <bug-100124-4-ykUXF30W5a@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100124-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100124
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #3)
> The reason why G++ rejects structs with a flexible array as the sole member
> is because GCC (in C mode) doesn't accept them. Git log indicates that GCC
> started rejecting such code in r38705
Note this change was done long before clang was around so it would be
interesting to know why clang chose differently.
next prev parent reply other threads:[~2021-04-17 0:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 20:18 [Bug c/100124] New: " gcc at behdad dot org
2021-04-16 20:50 ` [Bug c++/100124] " pinskia at gcc dot gnu.org
2021-04-16 21:02 ` jakub at gcc dot gnu.org
2021-04-17 0:03 ` msebor at gcc dot gnu.org
2021-04-17 0:51 ` pinskia at gcc dot gnu.org [this message]
2021-04-17 21:13 ` msebor at gcc dot gnu.org
2021-04-20 19:32 ` gcc at behdad dot org
2021-04-20 20:30 ` pinskia at gcc dot gnu.org
2021-04-20 22:16 ` gcc at behdad dot org
2021-04-26 22:26 ` msebor 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-100124-4-ykUXF30W5a@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).