Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA][5/5] New port: Cell BE SPU (testsuite tweaks)
Date: Wed, 22 Nov 2006 14:27:00 -0000	[thread overview]
Message-ID: <20061122142705.GB1120@nevyn.them.org> (raw)
In-Reply-To: <200611111840.kABIeGfq032402@d12av02.megacenter.de.ibm.com>

On Sat, Nov 11, 2006 at 07:40:16PM +0100, Ulrich Weigand wrote:
> Hello,
> 
> this adds a couple of tweaks related to SPU to the testsuite.  In particular,
> the following tests are disabled for the SPU:
> 
> gdb.base/attach.exp
>  -- because the runtime library doesn't provide "sleep"
> 
> gdb.base/term.exp
>  -- because we don't support command line arguments (by default)
> 
> gdb.cp/bs145503.exp
> gdb.cp/exception.exp
> gdb.cp/userdef.exp
>  -- because the executables are too big to execute on the SPU
>     (they pull in a lot of stuff from the libstdc++ library)
> 
> gdb.gdb/complaints.exp
> gdb.gdb/selftest.exp
> gdb.gdb/observer.exp
> gdb.gdb/xfullpath.exp
>  -- because the GDB executable is built for PowerPC and doesn't run on
>     the SPU (even though GDB considers the Cell BE configuration to be
>     'native')
> 
> OK?

How much of this still applies, now that you're building GDB using a
cross configuration triplet?  I would imagine isnative now fails.


-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2006-11-22 14:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-11 18:40 Ulrich Weigand
2006-11-22 14:16 ` [PING] " Ulrich Weigand
2006-11-22 14:27 ` Daniel Jacobowitz [this message]
2006-11-22 14:54   ` Ulrich Weigand
2006-11-22 16:11     ` Daniel Jacobowitz
2006-11-22 17:22       ` Ulrich Weigand

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=20061122142705.GB1120@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.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