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++/110242] ICE on valid (decltype with lambda)
Date: Thu, 29 Feb 2024 15:54:24 +0000	[thread overview]
Message-ID: <bug-110242-4-rRiaPArFMr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110242-4@http.gcc.gnu.org/bugzilla/>

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2024-02-29
     Ever confirmed|0                           |1
                 CC|                            |mpolacek at gcc dot gnu.org

--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed.

internal compiler error: error reporting routines re-entered.
0x10bc067 push_template_decl(tree_node*, bool)
        /home/mpolacek/src/gcc/gcc/cp/pt.cc:5883
0xed6ec4 start_preparsed_function(tree_node*, tree_node*, int)
        /home/mpolacek/src/gcc/gcc/cp/decl.cc:17845
0xf4eb00 start_lambda_function(tree_node*, tree_node*)
        /home/mpolacek/src/gcc/gcc/cp/lambda.cc:1696
0x1106d94 tsubst_lambda_expr(tree_node*, tree_node*, int, tree_node*)
        /home/mpolacek/src/gcc/gcc/cp/pt.cc:19748
0x11119fc tsubst_expr(tree_node*, tree_node*, int, tree_node*)
        /home/mpolacek/src/gcc/gcc/cp/pt.cc:21684
0x10f5523 tsubst(tree_node*, tree_node*, int, tree_node*)
        /home/mpolacek/src/gcc/gcc/cp/pt.cc:16895
0xf0be5a dump_template_bindings
        /home/mpolacek/src/gcc/gcc/cp/error.cc:494
0xf12a3d dump_substitution
        /home/mpolacek/src/gcc/gcc/cp/error.cc:1705
0xf14cb0 dump_function_decl
        /home/mpolacek/src/gcc/gcc/cp/error.cc:1878
0xf11580 dump_decl
        /home/mpolacek/src/gcc/gcc/cp/error.cc:1427
0xf1c053 decl_to_string
        /home/mpolacek/src/gcc/gcc/cp/error.cc:3323
0xf201a4 cp_printer
        /home/mpolacek/src/gcc/gcc/cp/error.cc:4501
0x36610a4 pp_format(pretty_printer*, text_info*, urlifier const*)
        /home/mpolacek/src/gcc/gcc/pretty-print.cc:1750
0x3661837 pp_format_verbatim(pretty_printer*, text_info*)
        /home/mpolacek/src/gcc/gcc/pretty-print.cc:1950
0x36620b9 pp_verbatim(pretty_printer*, char const*, ...)
        /home/mpolacek/src/gcc/gcc/pretty-print.cc:2200
0xf1e211 print_instantiation_full_context
        /home/mpolacek/src/gcc/gcc/cp/error.cc:3738
0xf1e79f maybe_print_instantiation_context
        /home/mpolacek/src/gcc/gcc/cp/error.cc:3888
0xf1c97e cp_diagnostic_starter
        /home/mpolacek/src/gcc/gcc/cp/error.cc:3574
0x3631f74 diagnostic_text_output_format::on_begin_diagnostic(diagnostic_info
const&)
        /home/mpolacek/src/gcc/gcc/diagnostic.cc:2401
0x362f4d7 diagnostic_context::report_diagnostic(diagnostic_info*)
        /home/mpolacek/src/gcc/gcc/diagnostic.cc:1605

  reply	other threads:[~2024-02-29 15:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13 21:05 [Bug c++/110242] New: " stevenxia990430 at gmail dot com
2024-02-29 15:54 ` mpolacek at gcc dot gnu.org [this message]
2024-02-29 16:02 ` [Bug c++/110242] " mpolacek at gcc dot gnu.org
2024-02-29 20:28 ` 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-110242-4-rRiaPArFMr@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).