All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Laurent Vivier <laurent@vivier.eu>, qemu-devel@nongnu.org
Cc: "Aurelien Jarno" <aurelien@aurel32.net>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH v2 1/7] target/m68k: add fscc.
Date: Mon, 26 Jun 2017 15:55:03 -0700	[thread overview]
Message-ID: <7661ca3e-6e2b-4522-b2b2-a2b81c72261d@twiddle.net> (raw)
In-Reply-To: <20170626220330.6785-2-laurent@vivier.eu>

On 06/26/2017 03:03 PM, Laurent Vivier wrote:
>       case 12: /* Unordered or Less Than A || (N && !Z) */
>       case 28: /* Not Greater than or Equal A || (N && !Z) */
> -        assert(FPSR_CC_Z == (FPSR_CC_N >> 1));
> -        tmp = tcg_temp_new();
> -        tcg_gen_xori_i32(tmp, fpsr, FPSR_CC_Z);
> -        tcg_gen_shli_i32(tmp, tmp, 1);
> -        tcg_gen_ori_i32(tmp, tmp, FPSR_CC_A);
> -        tcg_gen_and_i32(tmp, tmp, fpsr);
> -        tcg_gen_andi_i32(tmp, tmp, FPSR_CC_A | FPSR_CC_N);
> -        tcg_gen_brcondi_i32(TCG_COND_NE, tmp, 0, l1);
> +        g_assert(FPSR_CC_Z == (FPSR_CC_N >> 1));
> +        c->v1 = tcg_temp_new();
> +        c->g1 = 0;
> +        tcg_gen_xori_i32(c->v1, fpsr, FPSR_CC_Z);
> +        tcg_gen_shli_i32(c->v1, c->v1, 1);
> +        tcg_gen_ori_i32(c->v1, c->v1, FPSR_CC_A);
> +        tcg_gen_and_i32(c->v1, c->v1, fpsr);
> +        tcg_gen_andi_i32(c->v1, c->v1, FPSR_CC_A | FPSR_CC_N);
> +        c->tcond = TCG_COND_NE;

I think you're making a mistake wrt all of these shifts, in that you haven't 
masked out the other bits in FPSR.  Eventually you'll add support for the FPSR 
quotient and the byte below CC won't be zero.

Of course, one possibility is to deconstruct FPSR into pieces so that you can 
avoid extra masking.  Whether that's worthwhile, I don't know.

Another possibility for this one is

	tcg_gen_andi_i32(tmp, fpsr, FPSR_CC_Z);
	tcg_gen_shli_i32(tmp, tmp, ctz32(FPSR_CC_N) - ctz32(FPSR_CC_Z));
	tcg_gen_andc_i32(tmp, fpsr, tmp);
	tcg_gen_andi_i32(tmp, tmp, FPSR_CC_A | FPSR_CC_N);


r~

  reply	other threads:[~2017-06-26 22:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 22:03 [Qemu-devel] [PATCH v2 0/7] target/m68k: implement 680x0 FPU (part 2) Laurent Vivier
2017-06-26 22:03 ` [Qemu-devel] [PATCH v2 1/7] target/m68k: add fscc Laurent Vivier
2017-06-26 22:55   ` Richard Henderson [this message]
2017-06-26 22:03 ` [Qemu-devel] [PATCH v2 2/7] target/m68k: add fmovecr Laurent Vivier
2017-06-27 15:45   ` Philippe Mathieu-Daudé
2017-06-27 17:58     ` Laurent Vivier
2017-06-27 20:52       ` Philippe Mathieu-Daudé
2017-06-26 22:03 ` [Qemu-devel] [PATCH v2 3/7] target/m68k: add explicit single and double precision operations Laurent Vivier
2017-06-26 22:03 ` [Qemu-devel] [PATCH v2 4/7] softfloat: define floatx80_round() Laurent Vivier
2017-06-27 15:13   ` Laurent Vivier
2017-06-26 22:03 ` [Qemu-devel] [PATCH v2 5/7] target/m68k: add fsglmul and fsgldiv Laurent Vivier
2017-06-26 22:57   ` Richard Henderson
2017-06-26 22:03 ` [Qemu-devel] [PATCH v2 6/7] target/m68k: add explicit single and double precision operations (part 2) Laurent Vivier
2017-06-26 22:03 ` [Qemu-devel] [PATCH v2 7/7] target/m68k: add fmovem Laurent Vivier
2017-06-26 23:32   ` 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=7661ca3e-6e2b-4522-b2b2-a2b81c72261d@twiddle.net \
    --to=rth@twiddle.net \
    --cc=aurelien@aurel32.net \
    --cc=f4bug@amsat.org \
    --cc=laurent@vivier.eu \
    --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.