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 00:18:00 -0000 [thread overview]
Message-ID: <yov5heke6xx7.fsf@broadcom.com> (raw)
In-Reply-To: cgd@broadcom.com's message of "Sat, 8 Jun 2002 03:07:10 +0000 (UTC)"
At Sat, 8 Jun 2002 03:07:10 +0000 (UTC), cgd@broadcom.com wrote:
> [ tested in the same way as described in
> http://sources.redhat.com/ml/gdb-patches/2002-06/msg00103.html, but
> with a mipsisa64-elf target hacked to use the -mips64 multilib. ]
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...
So, i've got some bug-hunting to do.
Not worried about it screwing people up, because mipsisa64-elf isn't
even a supported in gcc right now. 8-)
chris
next prev parent reply other threads:[~2002-06-08 7:18 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 [this message]
2002-06-08 23:22 ` cgd
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=yov5heke6xx7.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