public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/112365] [12/13/14 Regression] ICE on invalid C++
Date: Fri, 03 Nov 2023 14:39:14 +0000 [thread overview]
Message-ID: <bug-112365-4-aQMZRc80Xi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112365-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112365
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P5
Ever confirmed|0 |1
Summary|ICE on invalid C++ |[12/13/14 Regression] ICE
| |on invalid C++
Last reconfirmed| |2023-11-03
Status|UNCONFIRMED |NEW
Target Milestone|14.0 |12.4
CC| |mpolacek at gcc dot gnu.org
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Started with r12-3324:
commit e902136b310ee17d4b49eb42d9d5e487d5dcf4a1
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Sep 3 09:46:32 2021 +0200
c++, abi: Set DECL_FIELD_CXX_ZERO_WIDTH_BIT_FIELD on C++ zero width
bitfields [PR102024]
next prev parent reply other threads:[~2023-11-03 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 8:15 [Bug c++/112365] New: [14 regression] " sjames at gcc dot gnu.org
2023-11-03 8:33 ` [Bug c++/112365] " rguenth at gcc dot gnu.org
2023-11-03 14:26 ` [Bug c++/112365] " sjames at gcc dot gnu.org
2023-11-03 14:39 ` mpolacek at gcc dot gnu.org [this message]
2023-11-16 16:43 ` [Bug c++/112365] [12/13/14 Regression] ICE on invalid C++ since r12-3324 cvs-commit at gcc dot gnu.org
2023-11-16 16:44 ` 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-112365-4-aQMZRc80Xi@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).