[Bug demangler/102132] [nm] Stack overflow in demangler_path

[pinskia at gcc dot gnu.org via Gcc-bugs]

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

Andrew Pinski  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|NEW |RESOLVED

--- Comment #5 from Andrew Pinski  ---
Dup of bug 98886.

*** This bug has been marked as a duplicate of bug 98886 ***

[Bug demangler/102132] [nm] Stack overflow in demangler_path

[amodra at gmail dot com via Gcc-bugs]

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

Alan Modra  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||amodra at gmail dot com
 Ever confirmed|0   |1
Version|unknown |12.0
   Last reconfirmed||2021-09-05

--- Comment #4 from Alan Modra  ---
Yes, gcc's libiberty is still considered upstream of binutils' copy.

[Bug demangler/102132] [nm] Stack overflow in demangler_path

[irfanariq at kaist dot ac.kr via Gcc-bugs]

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

--- Comment #3 from Irfan Ariq  ---
Okay, I will move it to sourceware bugzilla. Thank you

[Bug demangler/102132] [nm] Stack overflow in demangler_path

[pinskia at gcc dot gnu.org via Gcc-bugs]

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

--- Comment #2 from Andrew Pinski  ---
(In reply to Richard Biener from comment #1)
> wrong bugzilla, libiberty is a component in the sourceware bugzilla.

GCC's copy of libiberty is/was considered the upstream copy at least at one
point.

[Bug demangler/102132] [nm] Stack overflow in demangler_path

[rguenth at gcc dot gnu.org via Gcc-bugs]

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

--- Comment #1 from Richard Biener  ---
wrong bugzilla, libiberty is a component in the sourceware bugzilla.