fp-hw-survey capture: Apple Silicon (M-series, arm64/macOS)

Open Beginner friendly

#166 opened on Jun 9, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 1/5
Estimated time: Under an hour
Newbie friendliness: 84/100

Issue type: Feature
Clarity: Clearly specified
Activity status: Quiet
Tech stack: macos, rust
Domain: cli, operating-systems, tooling

Research direction

Use an Apple Silicon Mac and run the listed cargo build command for crates/fp-hw-survey. Run fp-hw-survey info and selftest first, then capture --label m-mac. Done means attaching the info output, clean selftest result, one-line NDJSON header, and resulting capture-*.ndjson file.

Written by the indexing model from the issue text.

Description

Capture native FP behavior on Apple Silicon (M1/M2/M3/M4, aarch64 / macOS) with crates/fp-hw-survey.

Steps

cargo build --release -p fp-hw-survey
./target/release/fp-hw-survey info        # confirm CPU brand + features (expect fp16; rpres/afp if present)
./target/release/fp-hw-survey selftest    # must pass
./target/release/fp-hw-survey capture --label m<N>-mac

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

fp16 is expected on all shipping M-series; rpres/afp recorded if detected.
Intra-ARMv8 estimate ops (frecpe/frsqrte/frecpx/fmulx) are predicted to be bit-identical with other ARMv8 parts — a zero-divergence merge against them is the expected, informative result.

Part of the FP hardware survey fleet-capture campaign.

Dominant language: C++
Stars: 2
Forks: 8
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Bug] NULL pointer dereference in llm_running_callback (NGZA-AX-LLM #3) Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

AXERA-TECH/ax-llm#77 · Opened Sep 22, 2026
resume() sends a second HTTP response (400) after a successful resume Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

games-on-whales/wolf#509 · Opened Sep 21, 2026
pn7160: reader goes permanently deaf — post-read IRQ-low check fails reads that succeeded Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

esphome/esphome#19452 · Opened Sep 21, 2026
Eval bug: Ministral-3 tool-calls during reasoning are not processed Open

bug-unconfirmed

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

ggml-org/llama.cpp#29248 · Opened Sep 21, 2026
run_tests.py fails on windows, but running tests individually works Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

NVIDIA/cuda-samples#453 · Opened Sep 21, 2026

More C++ issues