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++/109096] __has_unique_object_representations does not account for unnamed bitfield
Date: Tue, 14 Mar 2023 15:19:39 +0000 [thread overview]
Message-ID: <bug-109096-4-QOJjETYchA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109096-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109096
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:c35cf160a0ed81570cff6600dba465cf95fa80fa
commit r13-6663-gc35cf160a0ed81570cff6600dba465cf95fa80fa
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue Mar 14 16:17:32 2023 +0100
c++: Treat unnamed bitfields as padding for
__has_unique_object_representations [PR109096]
As reported in the PR, for __has_unique_object_representations we
were treating unnamed bitfields as named ones, which is wrong, they
are actually padding.
THe following patch fixes that.
2023-03-14 Jakub Jelinek <jakub@redhat.com>
PR c++/109096
* tree.cc (record_has_unique_obj_representations): Ignore unnamed
bitfields.
* g++.dg/cpp1z/has-unique-obj-representations3.C: New test.
next prev parent reply other threads:[~2023-03-14 15:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 21:52 [Bug c++/109096] New: " gcc at jonathanmueller dot dev
2023-03-10 22:04 ` [Bug c++/109096] " gcc at jonathanmueller dot dev
2023-03-10 22:21 ` pinskia at gcc dot gnu.org
2023-03-10 22:49 ` jakub at gcc dot gnu.org
2023-03-13 10:03 ` jakub at gcc dot gnu.org
2023-03-14 15:19 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-14 15:20 ` jakub at gcc dot gnu.org
2023-03-19 5:31 ` cvs-commit at gcc dot gnu.org
2023-03-20 10:30 ` jakub at gcc dot gnu.org
2023-05-02 20:15 ` cvs-commit at gcc dot gnu.org
2023-05-03 10:43 ` jakub at gcc dot gnu.org
2023-05-03 15:22 ` cvs-commit at gcc dot gnu.org
2023-05-04 7:25 ` jakub 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-109096-4-QOJjETYchA@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).