All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Alrae <leon.alrae@imgtec.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>, qemu-devel@nongnu.org
Cc: Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH] mips: Make CP0.Config4 and CP0.Config5 registers signed
Date: Wed, 5 Nov 2014 15:25:21 +0000	[thread overview]
Message-ID: <545A4161.40805@imgtec.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1411040311570.2881@tp.orcam.me.uk>

On 04/11/2014 15:37, Maciej W. Rozycki wrote:
> Make the data type used for the CP0.Config4 and CP0.Config5 registers 
> and their mask signed, for consistency with the remaining 32-bit CP0 
> registers, like CP0.Config0, etc.
> 
> Signed-off-by: Maciej W. Rozycki <macro@codesourcery.com>
> ---
> qemu-mips-config-int32_t.diff
> Index: qemu-git-trunk/target-mips/cpu.h
> ===================================================================
> --- qemu-git-trunk.orig/target-mips/cpu.h	2014-11-02 01:05:19.000000000 +0000
> +++ qemu-git-trunk/target-mips/cpu.h	2014-11-02 01:08:26.527563002 +0000
> @@ -372,11 +372,11 @@ struct CPUMIPSState {
>  #define CP0C3_MT   2
>  #define CP0C3_SM   1
>  #define CP0C3_TL   0
> -    uint32_t CP0_Config4;
> -    uint32_t CP0_Config4_rw_bitmask;
> +    int32_t CP0_Config4;
> +    int32_t CP0_Config4_rw_bitmask;
>  #define CP0C4_M    31
> -    uint32_t CP0_Config5;
> -    uint32_t CP0_Config5_rw_bitmask;
> +    int32_t CP0_Config5;
> +    int32_t CP0_Config5_rw_bitmask;
>  #define CP0C5_M          31
>  #define CP0C5_K          30
>  #define CP0C5_CV         29
> 

Reviewed-by: Leon Alrae <leon.alrae@imgtec.com>

      reply	other threads:[~2014-11-05 15:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 15:37 [Qemu-devel] [PATCH] mips: Make CP0.Config4 and CP0.Config5 registers signed Maciej W. Rozycki
2014-11-05 15:25 ` Leon Alrae [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=545A4161.40805@imgtec.com \
    --to=leon.alrae@imgtec.com \
    --cc=aurelien@aurel32.net \
    --cc=macro@codesourcery.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 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.