From: Michael Snyder <msnyder@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Michael Snyder <msnyder@cygnus.com>,
gdb-patches@sources.redhat.com, ezannoni@redhat.com
Subject: Re: [PATCH] Tweak tests for target with 4-byte doubles
Date: Thu, 23 May 2002 11:01:00 -0000 [thread overview]
Message-ID: <3CED281B.3F1F@redhat.com> (raw)
In-Reply-To: <3CED25E6.3080700@cygnus.com>
Andrew Cagney wrote:
>
> > 2002-05-23 Michael Snyder <msnyder@redhat.com>
> >
> > * gdb.base/all-bin.exp: Allow for reduced floating point precision.
> > * gdb.base/call-rt-st.exp: Ditto.
> >
> > Index: all-bin.exp
> > ===================================================================
> > RCS file: /cvs/src/src/gdb/testsuite/gdb.base/all-bin.exp,v
> > retrieving revision 1.2
> > diff -p -r1.2 all-bin.exp
> > *** all-bin.exp 6 Mar 2001 08:21:50 -0000 1.2
> > --- all-bin.exp 23 May 2002 15:40:03 -0000
> > *************** send_gdb "print v_int+v_double\n"
> > *** 189,198 ****
> > gdb_expect {
> > -re ".*206.56565.*$gdb_prompt $" {
> > pass "print value of v_int+v_double"
> > ! }
> > -re ".*$gdb_prompt $" { fail "print value of v_int+v_double" }
> > ! timeout { fail "(timeout) print value of v_int+" } ! }
> >
> > Michael,
> >
> > Last time this was raised it was concluded that GDB shouldn't be testing the FPU here. Rather than adding d10v specific hacks, reduce the precision of the value being checked.
>
> Hmm, to expand a little:
>
> > -re ".*206.56565.*$gdb_prompt $" {
>
> to
>
> -re ".*206.56\[0-9\]*
>
> so it isn't assuming a specific underlying floating-point representation.
>
Got it. Will do.
prev parent reply other threads:[~2002-05-23 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-23 8:52 Michael Snyder
2002-05-23 9:09 ` Andrew Cagney
2002-05-23 10:35 ` Andrew Cagney
2002-05-23 11:01 ` Michael Snyder [this message]
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=3CED281B.3F1F@redhat.com \
--to=msnyder@redhat.com \
--cc=ac131313@cygnus.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@cygnus.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