Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@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: Thu, 21 Nov 2013 23:43:01 +0100	[thread overview]
Message-ID: <20131121224301.GY10382@linux-mips.org> (raw)
In-Reply-To: <alpine.LFD.2.03.1311211934420.3267@linux-mips.org>

On Thu, Nov 21, 2013 at 07:52:04PM +0000, Maciej W. Rozycki wrote:

>  I think the discussion was off-list (Ralf, would you mind if I digged up 
> any clues from there?).

Please go ahead.

>  The format has been set long ago, and is also odd 
> enough to have 32 64-bit slots in the PTRACE_GETFPREGS/PTRACE_SETFPREGS 
> structure even for o32 processes (that now should be unexpectedly helpful 
> for FP64 o32 processes though), so there's little sense discussing its 
> prettiness or ugliness at this point in the game.
> 
>  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?

>  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.

  Ralf

  reply	other threads:[~2013-11-21 22:43 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 [this message]
2013-11-22  0:32         ` Maciej W. Rozycki
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=20131121224301.GY10382@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=paul.burton@imgtec.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