Skip to content

Add fallback for ARM Windows fp16 detection. #348

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
malfet merged 1 commit into from
Jan 27, 2026
Merged

Add fallback for ARM Windows fp16 detection. #348

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions src/arm/windows/init.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -249,6 +249,14 @@ static void set_cpuinfo_isa_fields(void) {
// guarantee that, but it holds in practice.
cpuinfo_isa.rdm = dotprod;

// PF_ARM_V82_FP16_INSTRUCTIONS_AVAILABLE may not be available in older
// Windows versions. If fp16arith was not detected with
// IsProcessorFeaturePresent(PF_ARM_V82_FP16_INSTRUCTIONS_AVAILABLE), fall

@fbarchard fbarchard Dec 1, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although this is true in practice, if the detection for FP16 is available and used, and it says false, we should respect that?
There have been recent A75 without FP16. They also dont have dot product.
Can you clarify a case for when this is necessary?

@edgchen1 edgchen1 Dec 1, 2025

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although this is true in practice, if the detection for FP16 is available and used, and it says false, we should respect that?

Yes, I agree that if detection is available, we should respect it. However, I am not sure that it is actually available. IsProcessorFeaturePresent() returns 0 both when the feature is actually not detected to be present and also when detection is not available.

Can you clarify a case for when this is necessary?

The behavior I observed was that, on a CI build system with an Ampere Altra processor, cpuinfo_has_arm_fp16_arith() used to return true (prior to the use of IsProcessorFeaturePresent(PF_ARM_V82_FP16_INSTRUCTIONS_AVAILABLE) in src/arm/windows/init.c) and then started to return false. On that same system, I was able to run a test program with NEON FP16 intrinsics successfully, so it appears that FP16 instructions are actually available.

@malfet malfet Jan 27, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds like an OS bug, has it been reported upstream?

// back to using the value of dotprod.
if (!cpuinfo_isa.fp16arith) {
cpuinfo_isa.fp16arith = dotprod;
}

/* Windows API reports all or nothing for cryptographic instructions. */
const bool crypto = IsProcessorFeaturePresent(PF_ARM_V8_CRYPTO_INSTRUCTIONS_AVAILABLE) != 0;
cpuinfo_isa.aes = crypto;
Expand Down