https://bugs.kde.org/show_bug.cgi?id=445668
--- Comment #9 from Mark Wielaard ---
(In reply to Nick Nethercote from comment #8)
> > The Rust compiler currently sometimes generates symbols with a
> > `.llvm.` suffix. These violate the v0 spec, which doesn't allow '.'
> > chars, and the
https://bugs.kde.org/show_bug.cgi?id=445668
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=445668
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=445668
--- Comment #11 from Mark Wielaard ---
(In reply to Nick Nethercote from comment #8)
> > The Rust compiler currently sometimes generates symbols with a
> > `.llvm.` suffix. These violate the v0 spec, which doesn't allow '.'
> > chars, and the
https://bugs.kde.org/show_bug.cgi?id=445668
--- Comment #8 from Nick Nethercote ---
> The Rust compiler currently sometimes generates symbols with a
> `.llvm.` suffix. These violate the v0 spec, which doesn't allow '.'
> chars, and the libiberty/Valgrind demangler doesn't demangle them. It's a
>
https://bugs.kde.org/show_bug.cgi?id=445668
--- Comment #7 from Nick Nethercote ---
The one-line fix works on the big example! Thank you.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=445668
--- Comment #6 from Mark Wielaard ---
I think I found it. rustc puts concrete function instances in namespaces (which
is allowed in DWARF since there is no strict separation between type
declarations and program scope entries in a DIE tree), the inline
https://bugs.kde.org/show_bug.cgi?id=445668
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=445668
--- Comment #4 from Nick Nethercote ---
Created attachment 143715
--> https://bugs.kde.org/attachment.cgi?id=143715=edit
Compiled file
Here's the binary produced by Rust 1.56.1 for `rustc -g a.rs` on my x86-64
Linux box.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=445668
--- Comment #3 from Nick Nethercote ---
Created attachment 143713
--> https://bugs.kde.org/attachment.cgi?id=143713=edit
Rust reproducer
I've written a tiny program that reproduces the problem.
- I compiled with Rust 1.56.1 with `rustc -g a.rs`.
- I
https://bugs.kde.org/show_bug.cgi?id=445668
--- Comment #2 from Nick Nethercote ---
> (*) BTW. What is this? It looks like a mangled Rust v0 symbol, but it isn't
> because it (I also checked with c++filt) cannot be demangled.
The Rust compiler currently sometimes generates symbols with a
https://bugs.kde.org/show_bug.cgi?id=445668
--- Comment #1 from Mark Wielaard ---
(In reply to Nick Nethercote from comment #0)
> Here is some DHAT output I am getting with Rust code:
>
> > └── PP 1.14/14 {
> > Total: 118,312 bytes (0.05%, 60.74/Minstr) in 11,864 blocks
> > (1.12%,
https://bugs.kde.org/show_bug.cgi?id=445668
Nick Nethercote changed:
What|Removed |Added
CC||m...@klomp.org
--
You are receiving this
13 matches
Mail list logo
