public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug rust/25025] FAIL: gdb.rust/generics.exp: print identity::<u32>(23u32) Date: Fri, 20 Mar 2020 16:16:11 +0000 [thread overview] Message-ID: <bug-25025-4717-6PGtakWfiD@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25025-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25025 --- Comment #3 from Tom Tromey <tromey at sourceware dot org> --- One weird thing I see is that the linkage names all demangle to the same thing: murgatroyd. nm ./outputs/gdb.rust/generics/generics |grep ident 000000000001a8d0 t _ZN14rustc_demangle2v06Parser5ident17hd246e8f232202204E 0000000000004e00 t _ZN8generics8identity17h0c3a5bc2a2b8859fE 0000000000004e10 t _ZN8generics8identity17h0fa0c53502fafa11E 0000000000004e20 t _ZN8generics8identity17h12f1c22e0bab1915E 0000000000004e30 t _ZN8generics8identity17h6555574b96ab1837E murgatroyd. nm -C ./outputs/gdb.rust/generics/generics |grep ident 000000000001a8d0 t rustc_demangle::v0::Parser::ident 0000000000004e00 t generics::identity 0000000000004e10 t generics::identity 0000000000004e20 t generics::identity 0000000000004e30 t generics::identity This shouldn't be the problem though. -- You are receiving this mail because: You are on the CC list for the bug.
next parent reply other threads:[~2020-03-20 16:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-25025-4717@http.sourceware.org/bugzilla/> 2020-03-20 16:16 ` tromey at sourceware dot org [this message] 2020-03-20 17:29 ` tromey at sourceware dot org 2020-03-24 15:35 ` tromey at sourceware dot org 2020-04-24 13:10 ` vries at gcc dot gnu.org 2020-04-24 21:36 ` cvs-commit at gcc dot gnu.org 2020-04-24 21:36 ` tromey at sourceware dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-25025-4717-6PGtakWfiD@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).