qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Phil Staub <phil.staub@windriver.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] MIPS: Correct FCR0 initialization
Date: Mon, 6 Aug 2012 11:21:53 -0700	[thread overview]
Message-ID: <20120806182153.GA4606@windriver.com> (raw)
In-Reply-To: <mailman.186707.1339511294.854.qemu-devel@nongnu.org>

On Tue, Jun 12, 2012 at 10:28:14AM -0400, qemu-devel-request@nongnu.org wrote:
> Date: Tue, 12 Jun 2012 07:14:45 -0700
> From: Richard Henderson <rth@twiddle.net>
> To: "Maciej W. Rozycki" <macro@codesourcery.com>
> Cc: qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
> Subject: Re: [Qemu-devel] [PATCH] MIPS: Correct FCR0 initialization
> Message-ID: <4FD74ED5.9010604@twiddle.net>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> On 2012-06-07 18:04, Maciej W. Rozycki wrote:
> >  I have verified this change with system emulation running the GDB test 
> > suite for the mips-sde-elf target (o32, big endian, 24Kf CPU emulated), 
> > there were 55 progressions and no regressions.
> > 
> > Signed-off-by: Maciej W. Rozycki <macro@codesourcery.com>
> > ---
> > 
> >  Sent on behalf of Nathan, who's since left the company.  Please apply.
> > 
> >   Maciej
> > 
> > qemu-mips-fcr0.diff
> > Index: qemu-git-trunk/target-mips/translate.c
> > ===================================================================
> > --- qemu-git-trunk.orig/target-mips/translate.c	2012-06-04 05:35:53.245610241 +0100
> > +++ qemu-git-trunk/target-mips/translate.c	2012-06-04 05:39:26.245563823 +0100
> > @@ -12776,6 +12776,7 @@ void cpu_state_reset(CPUMIPSState *env)
> >      env->CP0_SRSConf3 = env->cpu_model->CP0_SRSConf3;
> >      env->CP0_SRSConf4_rw_bitmask = env->cpu_model->CP0_SRSConf4_rw_bitmask;
> >      env->CP0_SRSConf4 = env->cpu_model->CP0_SRSConf4;
> > +    env->active_fpu.fcr0 = env->cpu_model->CP1_fcr0;
> 
> Reviewed-by: Richard Henderson <rth@twiddle.net>
> 
> 
> r~

What are the plans for this patch? It doesn't appear to have been
applied in any of the repository branches.

Thanks,
Phil

-- 
Phil Staub, Senior Member of Technical Staff, Wind River
Direct: 702.290.0470 Fax: 702.982.0085

       reply	other threads:[~2012-08-06 19:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.186707.1339511294.854.qemu-devel@nongnu.org>
2012-08-06 18:21 ` Phil Staub [this message]
2012-08-07 12:10   ` [Qemu-devel] [PATCH] MIPS: Correct FCR0 initialization Peter Maydell
2012-08-07 14:56     ` Phil Staub
2012-08-09 19:57     ` Blue Swirl
2012-08-09 20:01       ` Phil Staub
2012-08-09 20:36         ` Peter Maydell
2012-08-09 21:17           ` Phil Staub
2012-08-09 22:09             ` Maciej W. Rozycki
2012-08-09 22:23               ` Phil Staub
2012-08-10  8:48           ` Andreas Färber
2012-08-10  9:00             ` Peter Maydell
2012-08-10  9:13               ` Andreas Färber
2012-08-10 13:15                 ` Maciej W. Rozycki
2012-08-10 14:30                   ` Andreas Färber
2012-08-10 21:51                     ` Meador Inge
2012-08-10 23:16                     ` Maciej W. Rozycki
2012-06-08  1:04 Maciej W. Rozycki
2012-06-12 14:14 ` Richard Henderson

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=20120806182153.GA4606@windriver.com \
    --to=phil.staub@windriver.com \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).