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++/114536] wrong constant evaluation of std::bit_cast for bit fields
Date: Sun, 31 Mar 2024 10:25:54 +0000 [thread overview]
Message-ID: <bug-114536-4-Dvwx1RrIMx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114536-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114536
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Fedor Chelnokov from comment #2)
> May be just fail constant evaluation then instead of evaluating it to 0?
I suspect gcc is not rejecting it because the struct is just one unsigned char
and it is getting confused between that and the unsigned char.
next prev parent reply other threads:[~2024-03-31 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 10:13 [Bug c++/114536] New: " fchelnokov at gmail dot com
2024-03-31 10:19 ` [Bug c++/114536] " pinskia at gcc dot gnu.org
2024-03-31 10:22 ` fchelnokov at gmail dot com
2024-03-31 10:25 ` pinskia at gcc dot gnu.org [this message]
2024-03-31 10:26 ` redi at gcc dot gnu.org
2024-03-31 10:27 ` redi at gcc dot gnu.org
2024-03-31 19:28 ` pinskia at gcc dot gnu.org
2024-04-03 15:41 ` 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-114536-4-Dvwx1RrIMx@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).