public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Remove split_style::UNDERSCORE Date: Wed, 6 Dec 2023 17:22:35 +0000 (GMT) [thread overview] Message-ID: <20231206172235.6CB83385B537@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f5bf104621213b6e75f40e4b3becce6c465b05a8 commit f5bf104621213b6e75f40e4b3becce6c465b05a8 Author: Tom Tromey <tromey@adacore.com> Date: Fri Nov 10 14:13:23 2023 -0700 Remove split_style::UNDERSCORE The recent changes to the way Ada names are matched means that split_style::UNDERSCORE is no longer used. This patch removes it. Diff: --- gdb/split-name.c | 13 ------------- gdb/split-name.h | 2 -- 2 files changed, 15 deletions(-) diff --git a/gdb/split-name.c b/gdb/split-name.c index 0805cb82700..4ef022cf58e 100644 --- a/gdb/split-name.c +++ b/gdb/split-name.c @@ -45,19 +45,6 @@ split_name (const char *name, split_style style) } break; - case split_style::UNDERSCORE: - /* Handle the Ada encoded (aka mangled) form here. */ - for (const char *iter = strstr (name, "__"); - iter != nullptr; - iter = strstr (iter, "__")) - { - result.emplace_back (&name[previous_len], - iter - &name[previous_len]); - iter += 2; - previous_len = iter - name; - } - break; - case split_style::DOT_STYLE: /* D and Go-style names. */ for (const char *iter = strchr (name, '.'); diff --git a/gdb/split-name.h b/gdb/split-name.h index ad2862e222d..2674c9b8d27 100644 --- a/gdb/split-name.h +++ b/gdb/split-name.h @@ -33,8 +33,6 @@ enum class split_style /* Split at ".". Used by Ada, Go, D. This has a funny name to work around a bug in Bison 2.3, which is used on macOS. */ DOT_STYLE, - /* Split at "__". Used by Ada encoded names. */ - UNDERSCORE, }; /* Split NAME into components at module boundaries. STYLE indicates
reply other threads:[~2023-12-06 17:22 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231206172235.6CB83385B537@sourceware.org \ --to=tromey@sourceware.org \ --cc=gdb-cvs@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).