From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 1/2] target-sh4: fix 64-bit fmov to/from memory
Date: Fri, 21 Nov 2008 22:46:32 +0100 [thread overview]
Message-ID: <20081121214632.GQ21493@volta.aurel32.net> (raw)
In-Reply-To: <yw1xd4go7oy4.fsf@thrashbarg.mansr.com>
On Fri, Nov 21, 2008 at 09:24:03PM +0000, Måns Rullgård wrote:
> Aurelien Jarno <aurelien@aurel32.net> writes:
>
> > On Fri, Nov 21, 2008 at 07:55:41PM +0000, Mans Rullgard wrote:
> >> When loading/storing a register pair, the even-numbered register
> >> always maps to the low 32 bits of memory independently of target
> >> endian configuration.
> >>
> >> Signed-off-by: Mans Rullgard <mans@mansr.com>
> >> ---
> >> target-sh4/translate.c | 63 ++++++++++++++++++++++++-----------------------
> >> 1 files changed, 32 insertions(+), 31 deletions(-)
> >>
> >> diff --git a/target-sh4/translate.c b/target-sh4/translate.c
> >> index 84a3f40..2d6dfe6 100644
> >> --- a/target-sh4/translate.c
> >> +++ b/target-sh4/translate.c
> >> @@ -991,31 +991,35 @@ static void _decode_opc(DisasContext * ctx)
> >> return;
> >> case 0xf00a: /* fmov {F,D,X}Rm,@Rn - FPSCR: Nothing */
> >> if (ctx->fpscr & FPSCR_SZ) {
> >> - TCGv_i64 fp = tcg_temp_new_i64();
> >> - gen_load_fpr64(fp, XREG(B7_4));
> >> - tcg_gen_qemu_st64(fp, REG(B11_8), ctx->memidx);
> >> - tcg_temp_free_i64(fp);
> >> + TCGv addr_hi = tcg_temp_new();
> >> + int fr = XREG(B7_4);
> >> + tcg_gen_addi_i32(addr_hi, REG(B11_8), 4);
> >> + tcg_gen_qemu_st32(cpu_fregs[fr ], REG(B11_8), ctx->memidx);
> >> + tcg_gen_qemu_st32(cpu_fregs[fr+1], addr_hi, ctx->memidx);
> >> + tcg_temp_free(addr_hi);
> >
> > You are totally breaking the indendation. Care to resend this patch with
> > a proper indentation?
>
> I was told to use spaces for indentation even if surrounding code uses
> tabs. I'll be happy to convert it to tabs if that's what you want.
>
The current file use tabs. While it is not consistent with other qemu
files, I think mixed indentation is even worse.
Please use tabs in your patch, and if you really like to you can send a
patch to convert the indentation of the whole file to spaces, but please
do it in a separate patch.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
next prev parent reply other threads:[~2008-11-21 21:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 19:55 [Qemu-devel] [PATCH 1/2] target-sh4: fix 64-bit fmov to/from memory Mans Rullgard
2008-11-21 19:55 ` [Qemu-devel] [PATCH 2/2] target-sh4: implement ftrv instruction Mans Rullgard
2009-02-03 20:28 ` Aurelien Jarno
2008-11-21 20:38 ` [Qemu-devel] [PATCH 1/2] target-sh4: fix 64-bit fmov to/from memory Aurelien Jarno
2008-11-21 21:24 ` [Qemu-devel] " Måns Rullgård
2008-11-21 21:46 ` Aurelien Jarno [this message]
2008-11-21 22:23 ` [Qemu-devel] [PATCH] " Mans Rullgard
2008-11-21 23:02 ` Aurelien Jarno
2008-11-21 23:30 ` [Qemu-devel] " Måns Rullgård
2008-11-21 23:55 ` Aurelien Jarno
2008-11-22 0:51 ` [Qemu-devel] " Mans Rullgard
2008-11-22 10:09 ` Aurelien Jarno
2008-11-21 22:25 ` [Qemu-devel] Re: [PATCH 1/2] " Måns Rullgård
-- strict thread matches above, loose matches on Subject: below --
2008-11-21 0:46 [Qemu-devel] " Mans Rullgard
2008-11-21 19:56 ` [Qemu-devel] " Måns Rullgård
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=20081121214632.GQ21493@volta.aurel32.net \
--to=aurelien@aurel32.net \
--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.