https://bugs.kde.org/show_bug.cgi?id=445668
--- Comment #9 from Mark Wielaard <m...@klomp.org> --- (In reply to Nick Nethercote from comment #8) > > The Rust compiler currently sometimes generates symbols with a > > `.llvm.<numbers>` suffix. These violate the v0 spec, which doesn't allow '.' > > chars, and the libiberty/Valgrind demangler doesn't demangle them. It's a > > problem that needs to be fixed on the Rust side. > > Going back to this (and I know it's a tangent), there's now some > disagreement about whether this needs to be fixed on the Rust side, or the > libiberty/Valgrind side: > https://github.com/rust-lang/rust/issues/60705#issuecomment-974011409 :( Interesting. I see gcc "fixed" this (for c++ symbols) by translating those suffixes to "[clone .constprop.2]", "[clone .isra.3]" or "[clone ._omp_fn.2]". Which is nice if you want to know why there is a new (local) symbol for a code range. But I think it would actually be fine to simply cut off anything after a '.' or '$' and just demangle the part before it. For the user the important thing is knowing which (source) function an address is associated with, not which compiler transformation has been applied to it. -- You are receiving this mail because: You are watching all bug changes.
