public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug other/59518] New: C++ demangler does not handle some global constructor & LTO names
@ 2013-12-16 1:03 d.g.gorbachev at gmail dot com
2024-04-03 4:15 ` [Bug demangler/59518] " pinskia at gcc dot gnu.org
2024-04-03 12:06 ` egallager at gcc dot gnu.org
0 siblings, 2 replies; 3+ messages in thread
From: d.g.gorbachev at gmail dot com @ 2013-12-16 1:03 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59518
Bug ID: 59518
Summary: C++ demangler does not handle some global constructor
& LTO names
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: d.g.gorbachev at gmail dot com
These names are not currently demangled: `_GLOBAL__sub_I__Z3foov',
`_GLOBAL__sub_I_bar', `_ZL1n.lto_priv.7', `_ZZ3foovE12__FUNCTION__.lto_priv.8',
`_ZStL8__ioinit.lto_priv.412'. (Although look similar, these names are
demangled: `_GLOBAL__I_65535_0_cp_lang.o.1915128', `_ZL3foov.lto_priv.9').
^ permalink raw reply [flat|nested] 3+ messages in thread* [Bug demangler/59518] C++ demangler does not handle some global constructor & LTO names 2013-12-16 1:03 [Bug other/59518] New: C++ demangler does not handle some global constructor & LTO names d.g.gorbachev at gmail dot com @ 2024-04-03 4:15 ` pinskia at gcc dot gnu.org 2024-04-03 12:06 ` egallager at gcc dot gnu.org 1 sibling, 0 replies; 3+ messages in thread From: pinskia at gcc dot gnu.org @ 2024-04-03 4:15 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59518 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |54254 Ever confirmed|0 |1 Last reconfirmed| |2024-04-03 Status|UNCONFIRMED |NEW --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- _GLOBAL__sub_ issue is PR 54254 Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54254 [Bug 54254] libiberty: demangling for global constructor is broken since r167781 ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug demangler/59518] C++ demangler does not handle some global constructor & LTO names 2013-12-16 1:03 [Bug other/59518] New: C++ demangler does not handle some global constructor & LTO names d.g.gorbachev at gmail dot com 2024-04-03 4:15 ` [Bug demangler/59518] " pinskia at gcc dot gnu.org @ 2024-04-03 12:06 ` egallager at gcc dot gnu.org 1 sibling, 0 replies; 3+ messages in thread From: egallager at gcc dot gnu.org @ 2024-04-03 12:06 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59518 Eric Gallager <egallager at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |egallager at gcc dot gnu.org --- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> --- (In reply to Andrew Pinski from comment #1) > _GLOBAL__sub_ issue is PR 54254 How about the others? ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-04-03 12:06 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2013-12-16 1:03 [Bug other/59518] New: C++ demangler does not handle some global constructor & LTO names d.g.gorbachev at gmail dot com 2024-04-03 4:15 ` [Bug demangler/59518] " pinskia at gcc dot gnu.org 2024-04-03 12:06 ` egallager at gcc dot gnu.org
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).