public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/114657] Invalid type conversion from some _BitInt bit-fields
Date: Tue, 09 Apr 2024 14:01:10 +0000	[thread overview]
Message-ID: <bug-114657-4-NIT7NNbrc1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114657-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114657

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
In particular, 6.5.1.1/2 says
"The type of the controlling expression is the type of the expression as if it
had undergone an lvalue conversion, array to pointer conversion, or function to
pointer conversion."
but doesn't list integer promotions (if those were to occur, you'd e.g. never
be able to match a char, signed char, unsigned char, short, unsigned short
types with _Generic because everything would be promoted to int.

  parent reply	other threads:[~2024-04-09 14:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09 13:36 [Bug c/114657] New: " juuso.alasuutari at gmail dot com
2024-04-09 13:54 ` [Bug c/114657] " jakub at gcc dot gnu.org
2024-04-09 14:01 ` jakub at gcc dot gnu.org [this message]
2024-04-09 14:37 ` jsm28 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-114657-4-NIT7NNbrc1@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).