public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "guojiufu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105418] debug_tree does not support well for std::construct_at Date: Fri, 29 Apr 2022 05:32:23 +0000 [thread overview] Message-ID: <bug-105418-4-735eZQd7Ls@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105418-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105418 --- Comment #5 from Jiu Fu Guo <guojiufu at gcc dot gnu.org> --- 0x1089f887 dump_substitution /home/guojiufu/gcc/gcc-mainline-base/gcc/cp/error.cc:1654 0x108a1c2f dump_function_decl /home/guojiufu/gcc/gcc-mainline-base/gcc/cp/error.cc:1817 0x1089e187 dump_decl /home/guojiufu/gcc/gcc-mainline-base/gcc/cp/error.cc:1385 0x108aa8df decl_as_string(tree_node*, int) /home/guojiufu/gcc/gcc-mainline-base/gcc/cp/error.cc:3146 0x1094d6ef trees_out::insert(tree_node*, walk_kind) /home/guojiufu/gcc/gcc-mainline-base/gcc/cp/module.cc:4801 0x1096300f trees_out::decl_node(tree_node*, walk_kind) /home/guojiufu/gcc/gcc-mainline-base/gcc/cp/module.cc:8582 0x10965da3 trees_out::tree_node(tree_node*) /home/guojiufu/gcc/gcc-mainline-base/gcc/cp/module.cc:9104 0x109542c7 trees_out::core_vals(tree_node*) /home/guojiufu/gcc/gcc-mainline-base/gcc/cp/module.cc:5924 0x10959d4f trees_out::tree_node_vals(tree_node*) /home/guojiufu/gcc/gcc-mainline-base/gcc/cp/module.cc:7074 0x10964dab trees_out::tree_value(tree_node*) /home/guojiufu/gcc/gcc-mainline-base/gcc/cp/module.cc:8911 0x10965ddf trees_out::tree_node(tree_node*) /home/guojiufu/gcc/gcc-mainline-base/gcc/cp/module.cc:9109 0x109542c7 trees_out::core_vals(tree_node*) /home/guojiufu/gcc/gcc-mainline-base/gcc/cp/module.cc:5924 0x10959d4f trees_out::tree_node_vals(tree_node*) /home/guojiufu/gcc/gcc-mainline-base/gcc/cp/module.cc:7074 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. Hi Andrew and Richard, Thanks a lot! This issue happens when calling debug_tree/decl_as_string manually inside FE. At where overloaded functions (::new) are not resolved yet, and then cause 'tsubst' to be called. I see, it is not a good place to use debug_tree.
next prev parent reply other threads:[~2022-04-29 5:32 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-28 9:09 [Bug c++/105418] New: " guojiufu at gcc dot gnu.org 2022-04-28 9:11 ` [Bug c++/105418] " guojiufu at gcc dot gnu.org 2022-04-28 9:17 ` pinskia at gcc dot gnu.org 2022-04-28 9:18 ` pinskia at gcc dot gnu.org 2022-04-28 9:20 ` pinskia at gcc dot gnu.org 2022-04-28 9:20 ` pinskia at gcc dot gnu.org 2022-04-28 11:04 ` rguenth at gcc dot gnu.org 2022-04-29 5:32 ` guojiufu at gcc dot gnu.org [this message] 2022-04-29 5:57 ` guojiufu at gcc dot gnu.org 2022-04-29 5:58 ` guojiufu 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-105418-4-735eZQd7Ls@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: linkBe 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).