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++/54319] [9/10/11/12 Regression] empty class causes error while non-empty does not
Date: Wed, 28 Jul 2021 01:00:59 +0000 [thread overview]
Message-ID: <bug-54319-4-NllV7gEOdk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54319-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54319
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|empty class causes error |[9/10/11/12 Regression]
|while non-empty does not |empty class causes error
| |while non-empty does not
Target Milestone|--- |9.5
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #5)
> Note even the following X causes an error:
> struct X {int :1;};
>
> Maybe that will give a hint of where the bug is located.
Which makes this a regression even :).
The above with just one anonymous bitfield field is accepted until GCC 6.
But this should give even more of what is the underlaying bug.
next prev parent reply other threads:[~2021-07-28 1:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-19 3:37 [Bug c++/54319] New: Assignment to rvalue aschepler at gmail dot com
2012-08-19 7:30 ` [Bug c++/54319] " daniel.kruegler at googlemail dot com
2012-08-19 11:55 ` paolo.carlini at oracle dot com
2012-08-19 12:13 ` daniel.kruegler at googlemail dot com
2012-08-19 12:43 ` paolo.carlini at oracle dot com
2021-07-28 0:32 ` [Bug c++/54319] empty class causes error while non-empty does not pinskia at gcc dot gnu.org
2021-07-28 1:00 ` pinskia at gcc dot gnu.org [this message]
2021-07-28 1:08 ` [Bug c++/54319] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org
2021-07-28 1:12 ` pinskia at gcc dot gnu.org
2021-07-28 1:23 ` pinskia at gcc dot gnu.org
2021-07-28 2:30 ` pinskia at gcc dot gnu.org
2021-07-28 2:46 ` pinskia at gcc dot gnu.org
2021-07-28 2:49 ` pinskia at gcc dot gnu.org
2021-07-28 2:50 ` pinskia at gcc dot gnu.org
2022-01-17 15:21 ` rguenth at gcc dot gnu.org
2022-03-18 13:32 ` ppalka 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-54319-4-NllV7gEOdk@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).