https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105418
Jiu Fu Guo changed:
What|Removed |Added
Resolution|--- |INVALID
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105418
--- Comment #6 from Jiu Fu Guo ---
(In reply to Jiu Fu Guo from comment #5)
...
> 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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105418
--- Comment #5 from Jiu Fu Guo ---
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105418
Richard Biener changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105418
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2022-04-28
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105418
--- Comment #3 from Andrew Pinski ---
Debug_tree really only works post frontend in many cases. Especially when
things like overload sets are not resolved and all. You are better just to look
at the contents of the tree itself.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105418
Andrew Pinski changed:
What|Removed |Added
Severity|enhancement |trivial
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105418
--- Comment #2 from Andrew Pinski ---
I wonder if this is because the tree is jot fully constructed yet. Nor the
scope. So this issue might not be a bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105418
Jiu Fu Guo changed:
What|Removed |Added
Priority|P3 |P5
--- Comment #1 from Jiu Fu Guo ---
