qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: peer.adelt@c-lab.de, qemu-devel@nongnu.org
Cc: kbastian@mail.uni-paderborn.de
Subject: Re: [Qemu-devel] [PATCH 2/4] target-tricore: Added MADD.F and MSUB.F instructions
Date: Sat, 4 Jun 2016 09:55:17 -0700	[thread overview]
Message-ID: <a26dc7db-377b-e4bf-9e3c-74783c7c5c78@twiddle.net> (raw)
In-Reply-To: <1464562768-8954-3-git-send-email-peer.adelt@c-lab.de>

On 05/29/2016 03:59 PM, peer.adelt@c-lab.de wrote:
> +    flags = f_get_excp_flags(env);
> +    f_result = float32_muladd(-arg1, arg2, arg3, flags, &env->fp_status);

Bastian already pointed out that flags here is being used wrong,
but I thought I'd reinforce that "-arg1" is not how floating-point
negation works.  You need to use float_muladd_negate_product as
that 4th argument to float32_muladd.


r~

  parent reply	other threads:[~2016-06-04 16:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-29 22:59 [Qemu-devel] [PATCH 0/4] Added 5 instructions to the tricore target peer.adelt
2016-05-29 22:59 ` [Qemu-devel] [PATCH 1/4] target-tricore: Added FTOUZ instruction peer.adelt
2016-05-30  7:09   ` Bastian Koppelmann
2016-06-04 16:46   ` Richard Henderson
2016-05-29 22:59 ` [Qemu-devel] [PATCH 2/4] target-tricore: Added MADD.F and MSUB.F instructions peer.adelt
2016-05-31 11:13   ` Bastian Koppelmann
2016-06-04 16:55   ` Richard Henderson [this message]
2016-05-29 22:59 ` [Qemu-devel] [PATCH 3/4] target-tricore: Added new MOV instruction variant peer.adelt
2016-05-30  7:13   ` Bastian Koppelmann
2016-06-04 17:04   ` Richard Henderson
2016-05-29 22:59 ` [Qemu-devel] [PATCH 4/4] target-tricore: Added new JNE " peer.adelt
2016-05-30  8:17   ` Bastian Koppelmann

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=a26dc7db-377b-e4bf-9e3c-74783c7c5c78@twiddle.net \
    --to=rth@twiddle.net \
    --cc=kbastian@mail.uni-paderborn.de \
    --cc=peer.adelt@c-lab.de \
    --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).