From: cgd@broadcom.com
To: gdb-patches@sources.redhat.com
Subject: Re: [applied mips sim patch] better implementations of mul-acc ops.
Date: Sat, 08 Jun 2002 23:22:00 -0000 [thread overview]
Message-ID: <yov5d6v1as4q.fsf@broadcom.com> (raw)
In-Reply-To: cgd@broadcom.com's message of "08 Jun 2002 00:18:28 -0700"
At 08 Jun 2002 00:18:28 -0700, Chris G. Demetriou wrote:
> After checking it in (of course!), I looked at the test results some
> more, and found that, before and after, none of the tests which use
> the {,n}m{add,sub}.fmt instructions actually passed either before or
> after.
>
> Running with a simulator from a month ago but sources otherwise the
> same, they seem to work...
That wasn't actually true. Different tests passed, but not the ones
in question AFAICT. (The different tests that passed now fail due to
the unpredictable checking added to the MIPS32 & MIPS64 simulators.)
The cause of the problem with FP is discussed in:
http://gcc.gnu.org/ml/gcc/2002-06/msg00601.html
chris
prev parent reply other threads:[~2002-06-09 6:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-07 20:07 cgd
[not found] ` <mailpost.1023505630.3068@news-sj1-1>
2002-06-08 0:18 ` cgd
2002-06-08 23:22 ` cgd [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=yov5d6v1as4q.fsf@broadcom.com \
--to=cgd@broadcom.com \
--cc=gdb-patches@sources.redhat.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