From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Paul Burton <paul.burton@imgtec.com>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: R2300 (not the hay baler)
Date: Fri, 22 Nov 2013 00:32:04 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.03.1311220016030.3267@linux-mips.org> (raw)
In-Reply-To: <20131121224301.GY10382@linux-mips.org>
On Thu, 21 Nov 2013, Ralf Baechle wrote:
> > Also I'm not sure what the core file format is for the FP context, it may
> > be worth double-checking too.
>
> Is there some test suite for that kind of stuff?
GDB has some core file support coverage; I'm not sure if it's meticulous
enough to catch such issues though, and also if it checks OS-produced
cores or ones made with its own `generate-core-file' (aka `gcore') command
only. Besides if ptrace(2) and the core dumper are consistent with each
other, then chances are that any bugs there cancel each other too.
> > Please feel free to poke me directly if you have any further issues about
> > MIPS I ISA compatibility.
>
> Makes me wonder if there's a MIPS emulator that emulates a MIPS I system
> faithfully.
The Algorithmics FPU emulator (the original version shipped with their
SDE kit, not the kernel version we got contributed) could have been
strapped for true MIPS I support I believe. Also GNU sim might be able to
emulate a whole MIPS I CPU, although I haven't checked. Other than that I
haven't seen any (QEMU does not).
Maciej
next prev parent reply other threads:[~2013-11-22 0:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 11:07 R2300 (not the hay baler) Paul Burton
2013-11-19 11:21 ` Ralf Baechle
2013-11-19 11:31 ` Paul Burton
2013-11-19 12:27 ` Maciej W. Rozycki
2013-11-19 12:59 ` Paul Burton
2013-11-21 19:52 ` Maciej W. Rozycki
2013-11-21 22:43 ` Ralf Baechle
2013-11-22 0:32 ` Maciej W. Rozycki [this message]
2013-11-27 17:11 ` Paul Burton
2013-12-03 16:49 ` MASS MAILING: " Paul Burton
2013-11-19 13:09 ` Ralf Baechle
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=alpine.LFD.2.03.1311220016030.3267@linux-mips.org \
--to=macro@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=paul.burton@imgtec.com \
--cc=ralf@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.