fp-hw-survey capture: Snapdragon X-series (arm64/Windows-on-ARM)

[MikeGrier]

Capture native FP behavior on a Snapdragon X-series part (e.g. X Elite, aarch64 / Windows-on-ARM) with crates/fp-hw-survey.

Steps

cargo build --release -p fp-hw-survey
.\target\release\fp-hw-survey.exe info        # confirm CPU brand + features
.\target\release\fp-hw-survey.exe selftest    # must pass
.\target\release\fp-hw-survey.exe capture --label snapdragon-x-elite-win

What to attach to this issue

• The info output (CPU brand + detected features).
• The selftest result (must be clean — capture refuses to write otherwise).
• The one-line NDJSON header from the capture (durable provenance: cpu / os / features / date).
• The capture-*.ndjson file itself (attachment or link).

Notes

• On Windows-on-ARM there is no CPUID; brand comes from the registry ProcessorNameString, and fp16 from IsProcessorFeaturePresent. rpres/afp are best-effort here — Windows exposes no PF_* flag for them, so they may be absent from features even if the silicon supports them; note this when interpreting any single-precision estimate divergence.

Part of the FP hardware survey fleet-capture campaign.

[EmJayGee]

PS C:\GitHub\m> .\target\release\fp-hw-survey info
arch: aarch64
arch_tag: aarch64
os: windows
cpu: Snapdragon(R) X 12-core X1E80100 @ 3.40 GHz
features: fp16
catalogue: 77 ops
supported: 77 ops on this host
PS C:\GitHub\m> .\target\release\fp-hw-survey selftest
selftest passed: 11 checks on arch aarch64
PS C:\GitHub\m> .\target\release\fp-hw-survey capture --label "Surface 15inch Snapdragon X"
selftest passed (11 checks) on arch aarch64
budget of 157286400 bytes reached after 1452387 rows; stopping early
captured 73 ops, 1452387 rows -> capture-Surface_15inch_Snapdragon_X.ndjson
PS C:\GitHub\m>

capture-Surface_15inch_Snapdragon_x.zip