From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [FYI] Remove some unnecessary backslashes
Date: Wed, 27 Nov 2019 18:40:00 -0000 [thread overview]
Message-ID: <20191127183956.8181-1-tromey@adacore.com> (raw)
I found a couple of unnecessary backslashes in gdb. This removes
them.
Offhand, I wonder whether this abstract_to_concrete thing could be
done some other way? This seems possibly expensive.
Anyway, tested by rebuilding. I'm going to check this in as obvious.
gdb/ChangeLog
2019-11-27 Tom Tromey <tromey@adacore.com>
* dwarf2read.h (struct dwarf2_per_objfile): Remove unnecessary
backslashes.
* cp-support.c: Remove unnecessary backslashes.
Change-Id: I956c91ae24407eeafec8a731545b45f5222e6a9d
---
gdb/ChangeLog | 6 ++++++
gdb/cp-support.c | 2 +-
gdb/dwarf2read.h | 4 ++--
3 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/gdb/cp-support.c b/gdb/cp-support.c
index bec8dc86157..9286259f459 100644
--- a/gdb/cp-support.c
+++ b/gdb/cp-support.c
@@ -2006,7 +2006,7 @@ static std::string
quote (const char *str)
{
if (str != NULL)
- return std::string (1, '\"') + str + '\"';
+ return std::string (1, '"') + str + '"';
else
return "<null>";
}
diff --git a/gdb/dwarf2read.h b/gdb/dwarf2read.h
index 53fc7f4d9be..140bbed08ae 100644
--- a/gdb/dwarf2read.h
+++ b/gdb/dwarf2read.h
@@ -259,8 +259,8 @@ public:
/* Mapping from abstract origin DIE to concrete DIEs that reference it as
DW_AT_abstract_origin. */
- std::unordered_map<sect_offset, std::vector<sect_offset>, \
- gdb::hash_enum<sect_offset>> \
+ std::unordered_map<sect_offset, std::vector<sect_offset>,
+ gdb::hash_enum<sect_offset>>
abstract_to_concrete;
};
--
2.20.1
reply other threads:[~2019-11-27 18:40 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=20191127183956.8181-1-tromey@adacore.com \
--to=tromey@adacore.com \
--cc=gdb-patches@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: link
Be 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).