From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [pushed] Remove redundant check from parse_number.exp
Date: Tue, 26 Mar 2024 10:52:35 -0600 [thread overview]
Message-ID: <20240326165235.1308575-1-tromey@adacore.com> (raw)
A user on irc pointed out that parse_number.exp has a redundant check.
This patch removes the duplicate.
---
gdb/testsuite/gdb.base/parse_number.exp | 2 --
1 file changed, 2 deletions(-)
diff --git a/gdb/testsuite/gdb.base/parse_number.exp b/gdb/testsuite/gdb.base/parse_number.exp
index 648c34f5bc2..64ce14ccd65 100644
--- a/gdb/testsuite/gdb.base/parse_number.exp
+++ b/gdb/testsuite/gdb.base/parse_number.exp
@@ -110,8 +110,6 @@ proc parse_number { lang n } {
return [list "i64" $n]
} elseif { [fits_in_type $n 128 u] } {
return [list "i128" $n]
- } elseif { [fits_in_type $n 128 u] } {
- return [list "i128" $n]
} else {
# Overflow.
return [list $re_overflow $re_overflow]
--
2.43.0
reply other threads:[~2024-03-26 16:53 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=20240326165235.1308575-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