qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Gabriel Brookman <brookmangabriel@gmail.com>, qemu-devel@nongnu.org
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
	"Helge Deller" <deller@gmx.de>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Andreas Hüttel" <andreas.huettel@ur.de>,
	qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH] target/hppa: correct size bit parity for fmpyadd
Date: Fri, 17 Oct 2025 08:55:03 +0300	[thread overview]
Message-ID: <5ee3a3db-8fa2-426f-961b-aae09cb11c40@tls.msk.ru> (raw)
In-Reply-To: <20251009-hppa-correct-fmpyadd-size-bit-decoding-v1-1-f63bb6c3290c@gmail.com>

On 10/9/25 23:51, Gabriel Brookman wrote:
> For the fmpyadd instruction on the hppa architecture, there is a bit
> used to specify whether the instruction is operating on a 32 bit or 64
> bit floating point register. For most instructions, such a bit is 0 when
> operating on the smaller register and 1 when operating on the larger
> register. However, according to page 6-57 of the PA-RISC 1.1 Architecture
> and Instruction Set Reference Manual, this convention is reversed for the
> fmpyadd instruction specifically, meaning the bit is 1 for operations on
> 32 bit registers and 0 for 64 bit registers. Previously, QEMU decoded
> this operation as operating on the other size of register, leading to
> bugs when translating the fmpyadd instruction. This patch fixes that
> issue.
> 
> Reported-by: Andreas Hüttel <andreas.huettel@ur.de>
> Signed-off-by: Gabriel Brookman <brookmangabriel@gmail.com>
> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/3096
> ---
> Hi all,
> 
> This patch fixes the decoding of the fmpyadd instruction on the hppa
> target, which uses an inverted bit convention to select between
> 32-bit and 64-bit floating-point registers. The issue was reported by
> Andreas Hüttel after observing incorrect behavior when running real
> binaries under that target. He kindly submitted a minimal reproducer
> which I was able to use to debug the issue. I used this reproducer
> to verify correct operation after my fix.
> 
> Thanks,
> Gabriel
> 
> Reported-by: Andreas Hüttel
> ---
>   target/hppa/insns.decode | 8 ++++----
>   1 file changed, 4 insertions(+), 4 deletions(-)

I'm picking this up for qemu-stable (10.0 & 10.1).
Please let me know if I shouldn't.

Thanks,

/mjt

> diff --git a/target/hppa/insns.decode b/target/hppa/insns.decode
> index 4eaac750ea..13c6a55bf2 100644
> --- a/target/hppa/insns.decode
> +++ b/target/hppa/insns.decode
> @@ -365,10 +365,10 @@ fstd            011100 ..... ..... .. ............1.    @ldstim11
>   &mpyadd         rm1 rm2 ta ra tm
>   @mpyadd         ...... rm1:5 rm2:5 ta:5 ra:5 . tm:5     &mpyadd
>   
> -fmpyadd_f       000110 ..... ..... ..... ..... 0 .....  @mpyadd
> -fmpyadd_d       000110 ..... ..... ..... ..... 1 .....  @mpyadd
> -fmpysub_f       100110 ..... ..... ..... ..... 0 .....  @mpyadd
> -fmpysub_d       100110 ..... ..... ..... ..... 1 .....  @mpyadd
> +fmpyadd_f       000110 ..... ..... ..... ..... 1 .....  @mpyadd
> +fmpyadd_d       000110 ..... ..... ..... ..... 0 .....  @mpyadd
> +fmpysub_f       100110 ..... ..... ..... ..... 1 .....  @mpyadd
> +fmpysub_d       100110 ..... ..... ..... ..... 0 .....  @mpyadd
>   
>   ####
>   # Conditional Branches
> 
> ---
> base-commit: 94474a7733a57365d5a27efc28c05462e90e8944
> change-id: 20251009-hppa-correct-fmpyadd-size-bit-decoding-059501a0ae49
> 
> Best regards,



  parent reply	other threads:[~2025-10-17  5:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-09 20:51 [PATCH] target/hppa: correct size bit parity for fmpyadd Gabriel Brookman
2025-10-09 21:23 ` Richard Henderson
2025-10-09 21:30   ` [EXT] " Andreas K. Huettel
2025-10-09 21:32     ` Richard Henderson
2025-10-09 21:41   ` Helge Deller
2025-10-16  8:49 ` Philippe Mathieu-Daudé
2025-10-16 11:10   ` [EXT] " Andreas K. Huettel
2025-10-17  5:55 ` Michael Tokarev [this message]
2025-10-17  9:24   ` Helge Deller

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=5ee3a3db-8fa2-426f-961b-aae09cb11c40@tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=andreas.huettel@ur.de \
    --cc=brookmangabriel@gmail.com \
    --cc=deller@gmx.de \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=richard.henderson@linaro.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).