From: Joseph Myers <josmyers@redhat.com>
To: Martin Uecker <uecker@tugraz.at>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [C PATCH] Fix ICE for composite type for structs with unsigned bitfields [PR113492]
Date: Sat, 20 Jan 2024 23:36:51 +0000 (UTC) [thread overview]
Message-ID: <2140ab5d-8ec9-cded-7dfb-25239f82dc19@redhat.com> (raw)
In-Reply-To: <75930f8a30c3de6c45988fb0f8762ef07cad23a9.camel@tugraz.at>
On Sat, 20 Jan 2024, Martin Uecker wrote:
> C23: Fix ICE for composite type for structs with unsigned bitfields [PR113492]
>
> This patch fixes a bug when forming a composite type from structs that
> contain an unsigned bitfield declared with int while using -funsigned-bitfields.
> In such structs the unsigned integer type was not compatible to the
> regular unsigned integer type used elsewhere in the C FE.
>
> PR c/113492
>
> gcc/c:
> * c-decl.cc (grokdeclarator): Use c_common_unsigned_type instead of
> unsigned_type_for to create the unsigned type for bitfields declared
> with int when using -funsigned-bitfields.
>
> gcc/testsuite:
> * gcc.dg/pr113492.c: New test.
OK.
--
Joseph S. Myers
josmyers@redhat.com
prev parent reply other threads:[~2024-01-20 23:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 18:37 Martin Uecker
2024-01-20 23:36 ` Joseph Myers [this message]
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=2140ab5d-8ec9-cded-7dfb-25239f82dc19@redhat.com \
--to=josmyers@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=uecker@tugraz.at \
/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).