From: Daniel Jacobowitz <drow@false.org>
To: Paul Gilliam <pgilliam@us.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] test for altivec h/w on PowerPC
Date: Tue, 01 Mar 2005 23:28:00 -0000 [thread overview]
Message-ID: <20050301232850.GA29883@nevyn.them.org> (raw)
In-Reply-To: <200503011519.39739.pgilliam@us.ibm.com>
On Tue, Mar 01, 2005 at 03:19:39PM -0800, Paul Gilliam wrote:
> testsuite/gdb.arch/altivec-abi.exp and testsuite/gdb.arch/altivec-regs.exp
> test for relivance by checking if the configuration string ends in 'altivec'.
> This wasn't working for me and doesn't seem like the right way to do this.
>
> So I replaced it by adding a new routine to testsuit/lib/gdb.exp that compiles
> and runs a tiny little program. If we are on any machine that doesn't have
> altivec hardware, then either the compile fails or the tiny little program
> gets an illegal instruction trap when run. This is a modification of a
> similar routine in the gcc testsuite. (cut-and-paste code re-use)
>
> I then changed the two tests mentioned above to use the new routine.
>
> Ok to commit?
Not quite.
- You've missed a changelog entry.
- You're running a test on the build system instead of the target
system.
- This code is based on Janis's check_vmx_hw_available from GCC, so you
might want to give credit. Incidentally, the original version runs the
test on $target...
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-01 23:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 23:23 Paul Gilliam
2005-03-01 23:28 ` Daniel Jacobowitz [this message]
2005-03-02 0:36 ` Paul Gilliam
2005-03-02 1:56 ` Daniel Jacobowitz
2005-03-02 18:14 ` Paul Gilliam
2005-03-02 21:50 ` Paul Gilliam
2005-03-03 17:27 ` Daniel Jacobowitz
2005-03-10 0:43 ` Paul Gilliam
2005-03-28 23:45 ` Paul Gilliam
2005-03-29 20:43 ` Daniel Jacobowitz
2005-04-30 19:47 ` Daniel Jacobowitz
2005-05-03 0:48 ` [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=20050301232850.GA29883@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=pgilliam@us.ibm.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