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/113492] [14 Regression] ICE: in composite_type_internal, at c/c-typeck.cc:557 with -std=c2x -funsigned-bitfields since r14-6808
Date: Sat, 20 Jan 2024 08:39:34 +0000	[thread overview]
Message-ID: <bug-113492-4-30xuv2M0uy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113492-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ice-on-valid-code

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to uecker from comment #4)
> Yes, it is just weird because similar bugs for other new language features,
> e.g. an ICE for BitInt are not labeled as a regression and are P3.

-std=c2x is not a "new feature" in GCC 14 though, it was there in GCC 13. What
is a new feature is "constructing composite types for structs and unions" but
those rules might not be known by many users so it is only new feature
internally.

Also P3 just means not categorized yet; I forgot where that is documented.

  parent reply	other threads:[~2024-01-20  8:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 20:14 [Bug c/113492] New: [14 Regression] ICE: in composite_type_internal, at c/c-typeck.cc:557 with -std=c2x -funsigned-bitfields zsojka at seznam dot cz
2024-01-19  9:16 ` [Bug c/113492] " rguenth at gcc dot gnu.org
2024-01-19 16:04 ` [Bug c/113492] [14 Regression] ICE: in composite_type_internal, at c/c-typeck.cc:557 with -std=c2x -funsigned-bitfields since r14-6808 jakub at gcc dot gnu.org
2024-01-19 18:10 ` uecker at gcc dot gnu.org
2024-01-20  6:15 ` zsojka at seznam dot cz
2024-01-20  8:30 ` uecker at gcc dot gnu.org
2024-01-20  8:39 ` pinskia at gcc dot gnu.org [this message]
2024-01-20  8:48 ` uecker at gcc dot gnu.org
2024-01-20  9:08 ` [Bug c/113492] " zsojka at seznam dot cz
2024-01-20  9:11 ` pinskia at gcc dot gnu.org
2024-01-20  9:15 ` uecker at gcc dot gnu.org
2024-01-20 12:34 ` uecker at gcc dot gnu.org
2024-01-20 15:02 ` uecker at gcc dot gnu.org
2024-01-21 18:39 ` cvs-commit at gcc dot gnu.org
2024-01-31 20:01 ` uecker 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-113492-4-30xuv2M0uy@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).