From: Paul Gilliam <pgilliam@us.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] Allow altivec-{abi,regs}.c to be compiled by IBM's xlc compiler
Date: Wed, 30 Mar 2005 23:01:00 -0000 [thread overview]
Message-ID: <200503301456.56428.pgilliam@us.ibm.com> (raw)
In-Reply-To: <20050329204333.GB20646@nevyn.them.org>
On Tuesday 29 March 2005 12:43, Daniel Jacobowitz wrote
> Warning takes a string. TCL doesn't use semicolons.
OK, I've fixed those two things (I don't know how I missed the type of
argument to 'warning') and have included the revised patch below.
-=# Paul #=-
PS: semicolons ARE used in TCL - as statement separators. Of course in this
case they are redundent, being followed by a new-line, the other statement
separator 8-)
2005-03-09 Paul Gilliam <pgilliam@us.ibm.com>
* gdb.arch/altivec-abi.exp: Check for compiler and set 'use altivec'
flag accordingly.
* gdb.arch/altivec-regs.exp: Likewise.
Index: gdb.arch/altivec-abi.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.arch/altivec-abi.exp,v
retrieving revision 1.3
diff -c -3 -p -r1.3 altivec-abi.exp
*** gdb.arch/altivec-abi.exp 20 Jan 2003 15:40:07 -0000 1.3
--- gdb.arch/altivec-abi.exp 9 Mar 2005 19:25:34 -0000
*************** set testfile "altivec-abi"
*** 41,47 ****
set binfile ${objdir}/${subdir}/${testfile}
set srcfile ${testfile}.c
! if { [gdb_compile ${srcdir}/${subdir}/${srcfile} ${binfile} executable
{debug additional_flags=-w}] != "" } {
gdb_suppress_entire_file "Testcase compile failed, so all tests in this
file will automatically fail."
}
--- 41,62 ----
set binfile ${objdir}/${subdir}/${testfile}
set srcfile ${testfile}.c
! set compile_flags {debug additional_flags=-w}
! if [get_compiler_info $binfile] {
! warning "get_compiler failed"
! return -1
! }
!
! if [test_compiler_info gcc*] {
! set compile_flags "$compile_flags additional_flags=-maltivec"
! } elseif [test_compiler_info xlc*] {
! set compile_flags "$compile_flags additional_flags=-qaltivec"
! } else {
! warning "unknown compiler"
! return -1
! }
!
! if { [gdb_compile ${srcdir}/${subdir}/${srcfile} ${binfile} executable
$compile_flags] != "" } {
gdb_suppress_entire_file "Testcase compile failed, so all tests in this
file will automatically fail."
}
Index: gdb.arch/altivec-regs.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.arch/altivec-regs.exp,v
retrieving revision 1.2
diff -c -3 -p -r1.2 altivec-regs.exp
*** gdb.arch/altivec-regs.exp 20 Jan 2003 15:40:07 -0000 1.2
--- gdb.arch/altivec-regs.exp 9 Mar 2005 19:25:34 -0000
*************** set testfile "altivec-regs"
*** 41,47 ****
set binfile ${objdir}/${subdir}/${testfile}
set srcfile ${testfile}.c
! if { [gdb_compile ${srcdir}/${subdir}/${srcfile} ${binfile} executable
{debug additional_flags=-w}] != "" } {
gdb_suppress_entire_file "Testcase compile failed, so all tests in this
file will automatically fail."
}
--- 41,62 ----
set binfile ${objdir}/${subdir}/${testfile}
set srcfile ${testfile}.c
! set compile_flags {debug additional_flags=-w}
! if [get_compiler_info $binfile] {
! warning "get_compiler failed"
! return -1
! }
!
! if [test_compiler_info gcc*] {
! set compile_flags "$compile_flags additional_flags=-maltivec"
! } elseif [test_compiler_info xlc*] {
! set compile_flags "$compile_flags additional_flags=-qaltivec"
! } else {
! warning "unknown compiler"
! return -1
! }
!
! if { [gdb_compile ${srcdir}/${subdir}/${srcfile} ${binfile} executable
$compile_flags] != "" } {
gdb_suppress_entire_file "Testcase compile failed, so all tests in this
file will automatically fail."
}
next prev parent reply other threads:[~2005-03-30 23:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 20:56 Paul Gilliam
2005-03-29 20:42 ` Daniel Jacobowitz
2005-03-30 23:01 ` Paul Gilliam [this message]
2005-03-30 23:30 ` Daniel Jacobowitz
2005-04-01 18:44 ` Paul Gilliam
2005-04-01 18:47 ` [COMMIT] " Paul Gilliam
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=200503301456.56428.pgilliam@us.ibm.com \
--to=pgilliam@us.ibm.com \
--cc=drow@false.org \
--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