From: Fred Fish <fnf@specifix.com>
To: GDB Patches <gdb-patches@sources.redhat.com>
Subject: [PATCH] Fix apparent typo in lib/gdb.exp when setting skip_vmx_tests_saved
Date: Tue, 15 Aug 2006 18:45:00 -0000 [thread overview]
Message-ID: <200608151025.19801.fnf@specifix.com> (raw)
The attached patch fixes this error:
Running /src/latest/patched/src/gdb/gdb/testsuite/gdb.arch/altivec-abi.exp ...
ERROR: tcl error sourcing /src/latest/patched/src/gdb/gdb/testsuite/gdb.arch/altivec-abi.exp.
ERROR: can't read "skip_vmx_tests_saved": no such variable
while executing
"set $skip_vmx_tests_saved 1"
(procedure "skip_altivec_tests" line 15)
invoked from within
"skip_altivec_tests"
(file "/src/latest/patched/src/gdb/gdb/testsuite/gdb.arch/altivec-abi.exp" line 1)
("uplevel" body line 1)
invoked from within
"catch "uplevel #0 source $test_file_name""
===================================================================
2006-08-15 Fred Fish <fnf@specifix.com>
* lib/gdb.exp (skip_altivec_tests): Fix apparent typo,
'$' in front of skip_vmx_tests_saved when setting that.
Index: gdb/gdb/testsuite/lib/gdb.exp
===================================================================
RCS file: /cvsroots/latest/src/gdb/gdb/testsuite/lib/gdb.exp,v
retrieving revision 1.1.1.2.2.5
diff -u -p -r1.1.1.2.2.5 gdb.exp
--- gdb/gdb/testsuite/lib/gdb.exp 13 Aug 2006 20:57:17 -0000 1.1.1.2.2.5
+++ gdb/gdb/testsuite/lib/gdb.exp 15 Aug 2006 12:06:45 -0000
@@ -1196,7 +1196,7 @@ proc skip_altivec_tests {} {
# Some simulators are known to not support VMX instructions.
if { [istarget powerpc-*-eabi] || [istarget powerpc*-*-eabispe] } {
verbose "$me: target known to not support VMX, returning 1" 2
- return [set $skip_vmx_tests_saved 1]
+ return [set skip_vmx_tests_saved 1]
}
# Make sure we have a compiler that understands altivec.
next reply other threads:[~2006-08-15 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 18:45 Fred Fish [this message]
2006-08-18 8:49 ` Daniel Jacobowitz
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=200608151025.19801.fnf@specifix.com \
--to=fnf@specifix.com \
--cc=gdb-patches@sources.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