From: Daniel Jacobowitz <drow@false.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [rfc] add ppc testcase to test fpscr
Date: Tue, 02 Sep 2008 21:55:00 -0000 [thread overview]
Message-ID: <20080902215458.GB25623@caradoc.them.org> (raw)
In-Reply-To: <1219428669.8167.2.camel@localhost.localdomain>
On Fri, Aug 22, 2008 at 03:11:09PM -0300, Thiago Jung Bauermann wrote:
> +# Run the program, when the prompt comes back it will be for the invalid
> +# operation breakpoint.
> +gdb_test "run" "" ""
This is similar to what Joel said about testing bare metal targets -
using "run" will break gdbserver testing. Pick almost any test and you
can see how this is usually handled, e.g. by gdb_run_cmd or "runto
main".
> +# First, verify if FPSCR is all zeroes.
> +gdb_test "print \$fpscr" " = 0\r" "FPSCR is all zeroes"
Oh, also there's PowerPC targets without hardware floating
point... and GDB is sometimes smart enough nowadays to not display
dummy FP registers. So having fpscr not exist is legitimate.
There's also the E500, which does not have a classic FPU.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-09-02 21:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 23:18 Thiago Jung Bauermann
2008-08-21 23:32 ` Daniel Jacobowitz
2008-08-21 23:42 ` Thiago Jung Bauermann
2008-08-22 2:47 ` Daniel Jacobowitz
2008-08-22 18:13 ` Thiago Jung Bauermann
2008-09-02 21:40 ` Joel Brobecker
2008-09-02 23:35 ` Thiago Jung Bauermann
2008-09-02 23:46 ` Daniel Jacobowitz
2008-09-02 21:55 ` Daniel Jacobowitz [this message]
2008-09-03 20:15 ` Thiago Jung Bauermann
2008-09-03 21:01 ` Daniel Jacobowitz
2008-09-04 1:26 ` Thiago Jung Bauermann
2008-09-05 0:12 ` Joel Brobecker
2008-09-05 3:38 ` Thiago Jung Bauermann
2008-09-05 14:00 ` Joel Brobecker
2008-09-05 19:30 ` Thiago Jung Bauermann
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=20080902215458.GB25623@caradoc.them.org \
--to=drow@false.org \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
/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