From: Paul Gilliam <pgilliam@us.ibm.com>
To: gdb-patches@sources.redhat.com
Subject: Another altivec testsuite patch
Date: Wed, 02 Mar 2005 21:57:00 -0000 [thread overview]
Message-ID: <200503021353.50652.pgilliam@us.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 170 bytes --]
The gcc compiler needs -maltivec to enable altivec support.
OK to commit? Is this an obvious patch I should have just committed without
asking?
-=# Paul Gilliam #=-
[-- Attachment #2: altivec2.patch --]
[-- Type: text/x-diff, Size: 1964 bytes --]
diff -Naur testsuite.old/ChangeLog testsuite/ChangeLog
--- testsuite.old/ChangeLog 2005-03-02 13:28:23.757211464 -0800
+++ testsuite/ChangeLog 2005-03-02 13:56:01.659188904 -0800
@@ -1,3 +1,8 @@
+2005-03-02 Paul Gilliam <pgilliam@us.ibm.com>
+
+ * gdb.arch/altivec-abi.exp: Added -maltivec to compiler flags.
+ * gdb.arch/altivec-regs.exp: Likewise
+
2004-03-01 Paul Gilliam <pgilliam@us.ibm.com>
* lib/gdb.exp: added 'skip_altivec_tests', a modification of
diff -Naur testsuite.old/gdb.arch/altivec-abi.exp testsuite/gdb.arch/altivec-abi.exp
--- testsuite.old/gdb.arch/altivec-abi.exp 2005-03-02 13:28:23.759211160 -0800
+++ testsuite/gdb.arch/altivec-abi.exp 2005-03-02 13:30:27.210216176 -0800
@@ -41,7 +41,9 @@
set binfile ${objdir}/${subdir}/${testfile}
set srcfile ${testfile}.c
-if { [gdb_compile ${srcdir}/${subdir}/${srcfile} ${binfile} executable {debug additional_flags=-w}] != "" } {
+set compile_options {debug additional_flags=-w additional_flags=-maltivec}
+
+if { [gdb_compile ${srcdir}/${subdir}/${srcfile} ${binfile} executable $compile_options] != "" } {
gdb_suppress_entire_file "Testcase compile failed, so all tests in this file will automatically fail."
}
diff -Naur testsuite.old/gdb.arch/altivec-regs.exp testsuite/gdb.arch/altivec-regs.exp
--- testsuite.old/gdb.arch/altivec-regs.exp 2005-03-02 13:28:23.759211160 -0800
+++ testsuite/gdb.arch/altivec-regs.exp 2005-03-02 13:30:27.211216024 -0800
@@ -41,7 +41,9 @@
set binfile ${objdir}/${subdir}/${testfile}
set srcfile ${testfile}.c
-if { [gdb_compile ${srcdir}/${subdir}/${srcfile} ${binfile} executable {debug additional_flags=-w}] != "" } {
+set compile_options {debug additional_flags=-w additional_flags=-maltivec}
+
+if { [gdb_compile ${srcdir}/${subdir}/${srcfile} ${binfile} executable $compile_options] != "" } {
gdb_suppress_entire_file "Testcase compile failed, so all tests in this file will automatically fail."
}
next reply other threads:[~2005-03-02 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 21:57 Paul Gilliam [this message]
2005-03-03 17:27 ` 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=200503021353.50652.pgilliam@us.ibm.com \
--to=pgilliam@us.ibm.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