All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: "Riku Voipio" <riku.voipio@iki.fi>,
	"Andreas Färber" <afaerber@suse.de>,
	"Aurelien Jarno" <aurelien@aurel32.net>,
	"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] Merge mips64 and mipsn32
Date: Fri, 10 Feb 2012 23:16:09 +0000	[thread overview]
Message-ID: <201202102316.09638.paul@codesourcery.com> (raw)
In-Reply-To: <4F359E73.4000703@suse.de>

> > Make MIPS N32 be a variant of mips64, rather than a new architecture in
> > its own right.  This matches how sparc/ppc work, and makes TARGET_MIPS64
> > the right thing to check for a 64-bit mips core.
> > 
> > As side-effect of this is that linux-user/mipsn32 gets merged into
> > linux-user/mips64.  I consider this to be a feature as anything
> > differences other than the syscall numbers are probably bugs.
>...
> Note: Richard Henderson and me had been looking into code sharing among
> the MIPS ABIs for signal handling in response to a half-done Octeon
> mips64 patchset.
> 
> There's an unfinished RFC of mine from December or so, feel free to pick
> that up or to come up with a better idea!

Yeah, I found those and have a couple of other patches I need to reconcile and 
push out.  I haven't looked at the signal handling bits.

Paul

      reply	other threads:[~2012-02-10 23:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 11:23 [Qemu-devel] [PATCH] Merge mips64 and mipsn32 Paul Brook
2012-02-10 22:47 ` Andreas Färber
2012-02-10 23:16   ` Paul Brook [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=201202102316.09638.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=afaerber@suse.de \
    --cc=aurelien@aurel32.net \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    --cc=rth@twiddle.net \
    /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.