diff options
| author | Tom Tromey <tom@tromey.com> | 2024-03-30 13:48:30 -0600 |
|---|---|---|
| committer | Tom Tromey <tom@tromey.com> | 2024-04-02 13:30:19 -0600 |
| commit | ca2f7c84927f85b95f0f48f82b93f1460c372db4 (patch) | |
| tree | 35bb01e710e30a6f2878db2fc017f3350d5d7e24 /libgcc | |
| parent | 2f2924078ce51c2a0da3ad8f958f2d1de533969a (diff) | |
| download | gcc-ca2f7c84927f85b95f0f48f82b93f1460c372db4.zip gcc-ca2f7c84927f85b95f0f48f82b93f1460c372db4.tar.gz gcc-ca2f7c84927f85b95f0f48f82b93f1460c372db4.tar.bz2 | |
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.
Diffstat (limited to 'libgcc')
0 files changed, 0 insertions, 0 deletions