From: "Tom Tromey (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: gdb-patches@sourceware.org
Cc: Christian Biesinger <cbiesinger@google.com>,
Pedro Alves <palves@redhat.com>
Subject: [review] Remove "boolean" and "var_boolean" checks from ARI
Date: Thu, 12 Dec 2019 17:20:00 -0000 [thread overview]
Message-ID: <20191212172016.83C0120AF6@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1575560698000.Iaf449b51e8182ffa0b9ed25fe688e0ff64a07a67@gnutoolchain-gerrit.osci.io>
Tom Tromey has posted comments on this change.
Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/741
......................................................................
Patch Set 1:
(1 comment)
| --- /dev/null
| +++ /COMMIT_MSG
| @@ -1,0 +3,19 @@ Author: Tom Tromey <tromey@adacore.com>
| +AuthorDate: 2019-12-05 07:53:32 -0700
| +Commit: Tom Tromey <tromey@adacore.com>
| +CommitDate: 2019-12-05 07:53:32 -0700
| +
| +Remove "boolean" and "var_boolean" checks from ARI
| +
| +The "boolean" and "var_boolean" checks from ARI seem only to generate
| +false reports.
| +
| +Now that gdb is in C++, at least the "boolean" check seems unlikely to
PS1, Line 12:
> I don't understand, the check suggests using bool instead of boolean. So presumably it was added specifically for c++? Still seems fine to remove it since I don't know why anyone would write boolean.
I am not sure but it may refer to some older typedef?
I don't know but basically it's not relevant any longer.
| +ever generate a true report.
| +
| +The "var_boolean" check likewise doesn't seem valuable any more --
| +presumably this refers to some ancient way of doing things in gdb, and
| +isn't likely to find a bug in the future.
| +
| +Therefore, this patch removes these two checks.
| +
| +gdb/ChangeLog
--
Gerrit-Project: binutils-gdb
Gerrit-Branch: master
Gerrit-Change-Id: Iaf449b51e8182ffa0b9ed25fe688e0ff64a07a67
Gerrit-Change-Number: 741
Gerrit-PatchSet: 1
Gerrit-Owner: Tom Tromey <tromey@sourceware.org>
Gerrit-Reviewer: Pedro Alves <palves@redhat.com>
Gerrit-Reviewer: Tom Tromey <tromey@sourceware.org>
Gerrit-CC: Christian Biesinger <cbiesinger@google.com>
Gerrit-Comment-Date: Thu, 12 Dec 2019 17:20:16 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: Christian Biesinger <cbiesinger@google.com>
Gerrit-MessageType: comment
next prev parent reply other threads:[~2019-12-12 17:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 15:45 Tom Tromey (Code Review)
2019-12-05 16:47 ` Pedro Alves (Code Review)
2019-12-05 16:59 ` Christian Biesinger (Code Review)
2019-12-12 17:20 ` Tom Tromey (Code Review) [this message]
2019-12-12 17:51 ` [review v2] " Tom Tromey (Code Review)
2019-12-13 22:17 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-12-13 22:17 ` Sourceware to Gerrit sync (Code Review)
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=20191212172016.83C0120AF6@gnutoolchain-gerrit.osci.io \
--to=gerrit@gnutoolchain-gerrit.osci.io \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=gnutoolchain-gerrit@osci.io \
--cc=palves@redhat.com \
/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).