From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: gdb-patches ml <gdb-patches@sourceware.org>
Subject: [commit] remove extra verbose -log calls in testcases
Date: Fri, 05 Sep 2008 19:59:00 -0000 [thread overview]
Message-ID: <1220642085.10056.21.camel@localhost.localdomain> (raw)
As noticed by Joel in my FPSCR testcase, it's not usual to call verbose
twice. Committed the following.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
2008-09-05 Thiago Jung Bauermann <bauerman@br.ibm.com>
* gdb.arch/altivec-abi.exp: Remove extra verbose call.
* gdb.arch/altivec-regs.exp: Likewise.
* gdb.arch/vsx-regs.exp: Likewise.
diff --git a/gdb/testsuite/gdb.arch/altivec-abi.exp b/gdb/testsuite/gdb.arch/altivec-abi.exp
index 2d84013..358edb9 100644
--- a/gdb/testsuite/gdb.arch/altivec-abi.exp
+++ b/gdb/testsuite/gdb.arch/altivec-abi.exp
@@ -27,7 +27,6 @@ if $tracelevel then {
if {![istarget "powerpc*"] || [skip_altivec_tests]} then {
verbose "Skipping altivec abi tests."
- verbose -log "Skipping altivec abi tests."
return
}
diff --git a/gdb/testsuite/gdb.arch/altivec-regs.exp b/gdb/testsuite/gdb.arch/altivec-regs.exp
index 91f749a..b8d8dc0 100644
--- a/gdb/testsuite/gdb.arch/altivec-regs.exp
+++ b/gdb/testsuite/gdb.arch/altivec-regs.exp
@@ -30,7 +30,6 @@ set bug_id 0
if {![istarget "powerpc*"] || [skip_altivec_tests]} then {
verbose "Skipping altivec register tests."
- verbose -log "Skipping altivec register tests."
return
}
diff --git a/gdb/testsuite/gdb.arch/vsx-regs.exp b/gdb/testsuite/gdb.arch/vsx-regs.exp
index 006eb6d..18def60 100644
--- a/gdb/testsuite/gdb.arch/vsx-regs.exp
+++ b/gdb/testsuite/gdb.arch/vsx-regs.exp
@@ -32,7 +32,6 @@ set bug_id 0
if {![istarget "powerpc*"] || [skip_vsx_tests]} then {
verbose "Skipping vsx register tests."
- verbose -log "Skipping vsx register tests."
return
}
next reply other threads:[~2008-09-05 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 19:59 Thiago Jung Bauermann [this message]
2008-09-05 22:21 ` Joel Brobecker
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=1220642085.10056.21.camel@localhost.localdomain \
--to=bauerman@br.ibm.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