From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Tests for the target description XML parser
Date: Thu, 08 Mar 2007 23:20:00 -0000 [thread overview]
Message-ID: <20070308232029.GA17914@caradoc.them.org> (raw)
In-Reply-To: <200703082309.l28N9tqG012916@d12av02.megacenter.de.ibm.com>
On Fri, Mar 09, 2007 at 12:09:55AM +0100, Ulrich Weigand wrote:
> This causes a FAIL on spu, since the target supports only a
> single architecture, and the pattern requires two. This
> probably was not the intention?
Nope. You should probably detect that and skip the remaining tests in
that file.
I would have expected 'set architecture' to print both spu and
spu:256K, but that's not important.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-08 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 17:14 Daniel Jacobowitz
2007-03-08 23:10 ` Ulrich Weigand
2007-03-08 23:20 ` Daniel Jacobowitz [this message]
2007-03-09 0:05 ` Ulrich Weigand
2007-03-09 0:10 ` Daniel Jacobowitz
2007-03-09 0:14 ` 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=20070308232029.GA17914@caradoc.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