Binary identity and CPU optimization

Aner 0.0.3 keeps aner --version compatible with existing tools:

Aner 0.0.3

Run aner --binary to inspect the installed executable's target, compiled CPU profile and instruction baseline, build configuration, LTO, compiler, and numerical CPU backend. On macOS it also reports the running CPU separately. aner --binnary is accepted as an alias. For example, an M5 targeted release reports CPU optimization: Apple silicon M5 and CPU profile: apple-m5. The displayed CPU profile is build metadata, not a measurement of execution speed.

The default macOS Apple silicon installer uses an M1 instruction baseline for M1 through M5 compatibility, with Accelerate selecting numerical CPU kernels at runtime. Supplemental archives named aner-0.0.3-macos-arm64-apple-m1.tar.gz through aner-0.0.3-macos-arm64-apple-m5.tar.gz provide explicit compiler targets for each chip. Select the archive matching your Mac's chip. These supplemental archives do not change the bootstrap's compatible default package selection. The macOS minimum remains 26.0.

Compiler support is checked for C++ and Objective-C++. All profiles keep strict floating point semantics, and CPU targeting does not automatically enable GPU execution. Performance varies by workload; chip targeting is not evidence of a measured speedup.

A compiled archive is distinct from a hardware validated release. A compile-only package has nativeStartupVerified: false in its receipt; it was not executed on capable hardware. native-startup records only successful startup, and broader conformance and performance results must be stated separately. Windows and Linux binaries report their compiled architecture and compiler baseline without an Apple silicon optimization label.