Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Paul Gilliam <pgilliam@us.ibm.com>, gdb-patches@sources.redhat.com
Subject: Re: [patch] test for altivec h/w on PowerPC
Date: Sat, 30 Apr 2005 19:47:00 -0000	[thread overview]
Message-ID: <20050430194716.GA6713@nevyn.them.org> (raw)
In-Reply-To: <20050329204449.GC20646@nevyn.them.org>

On Tue, Mar 29, 2005 at 03:44:49PM -0500, Daniel Jacobowitz wrote:
> On Wed, Mar 09, 2005 at 04:38:16PM -0800, Paul Gilliam wrote:
> > Ok, I have made all the requested chanages and tested it on powerpc with and with out altivec.
> > 
> > NOTE: this patch depends on a previous patch so that gdb.arch/altivec-*.exp can compile their test programs.   The previous patch is here:
> > http://sources.redhat.com/ml/gdb-patches/2005-03/msg00157.html
> > 
> > 2005-03-09  Paul Gilliam <pgilliam@us.ibm.com>
> > 
> >         * lib/gdb.exp: New proc 'skip_altivec_tests'
> >         * gdb.arch/altivec-abi.exp, gdb.arch/altivec-regs.exp: Use the new proc.
> 
> OK.  Some more adjustment may be needed but let's wait and see.

Paul, you may have missed these approvals.  Going to commit these
patches?

BTW, please use the ChangeLog I suggested earlier in this thread; the
above is wrong.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-04-30 19:47 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
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 [this message]
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=20050430194716.GA6713@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