public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/30276] [gdb/symtab] function name is _Dmain instead of "D main" Date: Tue, 02 Apr 2024 20:06:57 +0000 [thread overview] Message-ID: <bug-30276-4717-1cLiiX3Dzk@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30276-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30276 --- Comment #10 from Sourceware Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b1741ab0dafd899889faab6e862094a325a6b83c commit b1741ab0dafd899889faab6e862094a325a6b83c Author: Tom Tromey <tom@tromey.com> Date: Sat Mar 30 13:48:30 2024 -0600 libiberty: Invoke D demangler when --format=auto Investigating GDB PR d/31580 showed that the libiberty demangler doesn't automatically demangle D mangled names. However, I think it should -- like C++ and Rust (new-style), D mangled names are readily distinguished by the leading "_D", and so the likelihood of confusion is low. The other non-"auto" cases in this code are Ada (where the encoded form could more easily be confused by ordinary programs) and Java (which is long gone, but which also shared the C++ mangling and thus was just an output style preference). This patch also fixed another GDB bug, though of course that part won't apply to the GCC repository. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31580 Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30276 libiberty * cplus-dem.c (cplus_demangle): Try the D demangler with "auto" format. * testsuite/d-demangle-expected: Add --format=auto test. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-04-02 20:07 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-27 10:46 [Bug symtab/30276] New: " vries at gcc dot gnu.org 2023-03-27 10:51 ` [Bug symtab/30276] " vries at gcc dot gnu.org 2023-03-27 11:29 ` vries at gcc dot gnu.org 2023-03-27 11:30 ` vries at gcc dot gnu.org 2023-03-27 11:37 ` vries at gcc dot gnu.org 2023-03-27 11:53 ` vries at gcc dot gnu.org 2023-03-27 15:05 ` tromey at sourceware dot org 2024-03-30 20:07 ` tromey at sourceware dot org 2024-03-30 20:09 ` tromey at sourceware dot org 2024-03-30 20:10 ` tromey at sourceware dot org 2024-04-02 20:06 ` cvs-commit at gcc dot gnu.org [this message] 2024-04-02 20:08 ` 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-30276-4717-1cLiiX3Dzk@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).