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++/106311] [12/13 Regression] internal compiler error in redeclare_class_template
Date: Fri, 15 Jul 2022 00:06:50 +0000 [thread overview]
Message-ID: <bug-106311-4-cRTitfzvbQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106311-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106311
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Target Milestone|--- |12.2
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
Last reconfirmed| |2022-07-15
Summary|internal compiler error in |[12/13 Regression] internal
|redeclare_class_template |compiler error in
| |redeclare_class_template
Keywords| |ice-on-invalid-code
Priority|P3 |P2
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Started with r12-7562. Patch:
--- a/gcc/cp/pt.cc
+++ b/gcc/cp/pt.cc
@@ -6377,7 +6377,8 @@ redeclare_class_template (tree type, tree parms, tree
cons)
{
auto_diagnostic_group d;
error ("template parameter %q+#D", tmpl_parm);
- inform (DECL_SOURCE_LOCATION (parm), "redeclared here as %q#D", parm);
+ inform (DECL_P (parm) ? DECL_SOURCE_LOCATION (parm) : input_location,
+ "redeclared here as %q#D", parm);
return false;
}
next prev parent reply other threads:[~2022-07-15 0:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 0:05 [Bug c++/106311] New: " mpolacek at gcc dot gnu.org
2022-07-15 0:06 ` mpolacek at gcc dot gnu.org [this message]
2022-07-26 12:04 ` [Bug c++/106311] [12/13 Regression] " cvs-commit at gcc dot gnu.org
2022-07-26 13:22 ` cvs-commit at gcc dot gnu.org
2022-07-26 13:24 ` 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-106311-4-cRTitfzvbQ@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).