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++/106259] [10/11/12/13 Regression] ICE in diag_mismatched_tags, at cp/parser.cc:33896
Date: Mon, 11 Jul 2022 19:23:27 +0000 [thread overview]
Message-ID: <bug-106259-4-ZXGEVKLIjb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106259-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106259
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|ICE in |[10/11/12/13 Regression]
|diag_mismatched_tags, at |ICE in
|cp/parser.cc:33896 |diag_mismatched_tags, at
| |cp/parser.cc:33896
Target Milestone|--- |10.5
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
CC| |mpolacek at gcc dot gnu.org,
| |msebor at gcc dot gnu.org
Priority|P3 |P2
Last reconfirmed| |2022-07-11
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed.
commit 04dd734b52de121853e1ea6b3c197a598b294e23
Author: Martin Sebor <msebor@gmail.com>
Date: Fri Mar 27 12:07:45 2020 -0400
c++: avoid -Wredundant-tags on a first declaration in use [PR 93824]
next prev parent reply other threads:[~2022-07-11 19:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 18:57 [Bug c++/106259] New: " gscfq@t-online.de
2022-07-11 19:23 ` mpolacek at gcc dot gnu.org [this message]
2022-07-11 19:29 ` [Bug c++/106259] [10/11/12/13 Regression] " mpolacek at gcc dot gnu.org
2023-02-28 20:43 ` mpolacek at gcc dot gnu.org
2023-03-01 16:12 ` mpolacek at gcc dot gnu.org
2023-03-01 17:05 ` mpolacek at gcc dot gnu.org
2023-03-02 16:02 ` cvs-commit at gcc dot gnu.org
2023-03-02 16:06 ` [Bug c++/106259] [10/11/12 " mpolacek at gcc dot gnu.org
2023-03-04 17:52 ` cvs-commit at gcc dot gnu.org
2023-03-04 18:16 ` [Bug c++/106259] [10/11 " mpolacek 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-106259-4-ZXGEVKLIjb@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).