qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: "Peter Maydell" <peter.maydell@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Deprecate nwfpe emulation?
Date: Mon, 27 Jan 2025 13:02:56 -0800	[thread overview]
Message-ID: <27599be5-9669-466e-8e34-4ec0831c91cc@linaro.org> (raw)
In-Reply-To: <CAFEAcA_BF_b8r8cOJVsk13qEQZg0BS5F16s9M6NFLQVHZBfq4Q@mail.gmail.com>

On 1/27/25 09:46, Peter Maydell wrote:
> On Mon, 27 Jan 2025 at 17:27, Philippe Mathieu-Daudé <philmd@linaro.org> wrote:
>> On 27/1/25 12:27, Peter Maydell wrote:
>>> We have one test case in check-tcg which purports to be checking
>>> iwMMXt. In fact it is doing no such thing: it runs the test without
>>> selecting an iwMMXt CPU, which means the iwMMXt insns are interpreted
>>> as FPA11 insns by the linux-user emulate_arm_fpa11() code. So the test
>>> prints garbage and then succeeds anyway.
>>
>> Uh...
> 
> It had me confused for a while, because I'd convinced myself
> by code inspection that we only enabled iwMMXt if you
> manually asked for a pxa2xx CPU and not in the default 'max'
> CPU, and then I found this test case that we were running
> with the default CPU type and which was apparently passing :-)

Any chance we can deprecate the fpa11 stuff too?

I see it's still enabled by the kernel for some boards,
but it depends on really old configury:

config FPE_NWFPE
         bool "NWFPE math emulation"
         depends on (!AEABI || OABI_COMPAT) && !THUMB2_KERNEL
         help
           Say Y to include the NWFPE floating point emulator in the kernel.
           This is necessary to run most binaries. Linux does not currently
           support floating point hardware so you need to say Y here even if
           your machine has an FPA or floating point co-processor podule.

No thumb2, no eabi, and oabi_compat enabled.
I suspect that's a very rare configuration these days.

I'll note the help message is somewhat dated.  :-)


r~


  reply	other threads:[~2025-01-27 21:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-27 11:27 [PATCH 0/2] target/arm: Deprecate iwMMXt emulation and associated CPUs Peter Maydell
2025-01-27 11:27 ` [PATCH 1/2] target/arm: deprecate the pxa2xx CPUs and iwMMXt emulation Peter Maydell
2025-01-27 11:27 ` [PATCH 2/2] tests/tcg/arm: Remove test-arm-iwmmxt test Peter Maydell
2025-01-27 16:13 ` [PATCH 0/2] target/arm: Deprecate iwMMXt emulation and associated CPUs Richard Henderson
2025-01-27 17:27 ` Philippe Mathieu-Daudé
2025-01-27 17:46   ` Peter Maydell
2025-01-27 21:02     ` Richard Henderson [this message]
2025-02-11 15:44       ` Deprecate nwfpe emulation? Peter Maydell

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=27599be5-9669-466e-8e34-4ec0831c91cc@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-arm@nongnu.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).