From: Richard Henderson <richard.henderson@linaro.org>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>,
Gabriel Brookman <brookmangabriel@gmail.com>,
qemu-devel@nongnu.org
Cc: Helge Deller <deller@gmx.de>, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [EXT] Re: [PATCH] target/hppa: correct size bit parity for fmpyadd
Date: Thu, 9 Oct 2025 14:32:03 -0700 [thread overview]
Message-ID: <f75c7149-bfef-4b7e-bbb9-548b2ff5d34c@linaro.org> (raw)
In-Reply-To: <10069660.lOV4Wx5bFT@pinacolada>
On 10/9/25 14:30, Andreas K. Huettel wrote:
> 2) The doc is probably page 6-18 (fig. 6-8) and 6-19 (table 6-16), where the
> f field for FMPYADD and FMPYSUB is documented.
Yep, that's it.
r~
next prev parent reply other threads:[~2025-10-09 21:32 UTC|newest]
Thread overview: 5+ 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 [this message]
2025-10-09 21:41 ` 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=f75c7149-bfef-4b7e-bbb9-548b2ff5d34c@linaro.org \
--to=richard.henderson@linaro.org \
--cc=brookmangabriel@gmail.com \
--cc=deller@gmx.de \
--cc=dilfridge@gentoo.org \
--cc=peter.maydell@linaro.org \
--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).