public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109039] [12/13 Regression] Miscompilation with no_unique_address and bitfields
Date: Mon, 06 Mar 2023 14:44:57 +0000 [thread overview]
Message-ID: <bug-109039-4-q1qzWIZ6zy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109039-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109039
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Miscompilation with |[12/13 Regression]
|no_unique_address and |Miscompilation with
|bitfields |no_unique_address and
| |bitfields
Known to fail| |12.2.0, 13.0
CC| |jason at gcc dot gnu.org,
| |ppalka at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=103681
Target Milestone|--- |12.3
Known to work| |11.3.0
--- Comment #1 from Patrick Palka <ppalka at gcc dot gnu.org> ---
Started with r12-6028-ga37e8ce3b66325, before which sizeof(S) == 4 and now
sizeof(S) == 2
next prev parent reply other threads:[~2023-03-06 14:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 10:46 [Bug c++/109039] New: " coillol at yandex dot ru
2023-03-06 14:44 ` ppalka at gcc dot gnu.org [this message]
2023-03-06 14:59 ` [Bug c++/109039] [12/13 Regression] " jakub at gcc dot gnu.org
2023-03-09 14:56 ` jakub at gcc dot gnu.org
2023-03-09 16:57 ` jakub at gcc dot gnu.org
2023-03-09 17:12 ` jakub at gcc dot gnu.org
2023-03-10 19:37 ` cvs-commit at gcc dot gnu.org
2023-03-10 19:45 ` [Bug c++/109039] [12 " jakub at gcc dot gnu.org
2023-03-19 5:30 ` cvs-commit at gcc dot gnu.org
2023-03-20 10:29 ` 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-109039-4-q1qzWIZ6zy@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).