public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "falemagn at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/112288] [11/12/13/14 Regression] ICE - internal compiler error: in instantiate_decl, at cp/pt.cc:26861 since r6-6830-g20a0c6f9bdbd78
Date: Fri, 03 Nov 2023 17:36:30 +0000 [thread overview]
Message-ID: <bug-112288-4-kIPI8p0B7n@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112288-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112288
--- Comment #9 from Fabio Alemagna <falemagn at gmail dot com> ---
(In reply to Patrick Palka from comment #8)
> The issue was probably latent before r6-6830. The testcase is kind of
> strange,
It's the "friend injection" technique. In this case, it's used to create a
compile-time counter. The specific test case uses templates in such a way as to
try and circumvent a diagnostic-related bug (bug #112267), which however
triggered this other bug.
next prev parent reply other threads:[~2023-11-03 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 12:07 [Bug c++/112288] New: internal compiler error: in instantiate_decl, at cp/pt.cc:26861 falemagn at gmail dot com
2023-10-30 12:09 ` [Bug c++/112288] " falemagn at gmail dot com
2023-10-30 14:22 ` [Bug c++/112288] [14 Regression] ICE - " rguenth at gcc dot gnu.org
2023-10-30 16:28 ` [Bug c++/112288] [11/12/13/14 " mpolacek at gcc dot gnu.org
2023-10-30 16:31 ` mpolacek at gcc dot gnu.org
2023-10-30 17:43 ` falemagn at gmail dot com
2023-10-30 17:57 ` pinskia at gcc dot gnu.org
2023-10-30 18:03 ` mpolacek at gcc dot gnu.org
2023-10-30 20:55 ` falemagn at gmail dot com
2023-11-03 17:27 ` [Bug c++/112288] [11/12/13/14 Regression] ICE - internal compiler error: in instantiate_decl, at cp/pt.cc:26861 since r6-6830-g20a0c6f9bdbd78 ppalka at gcc dot gnu.org
2023-11-03 17:36 ` falemagn at gmail dot com [this message]
2023-11-04 18:41 ` ppalka at gcc dot gnu.org
2024-05-07 7:42 ` [Bug c++/112288] [11/12/13/14/15 " rguenth 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-112288-4-kIPI8p0B7n@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).