Add runtime ARM SVE2 detection support

[iksaif]

Motivation

Enable deployment of a single zstd binary across heterogeneous ARM fleets with varying CPU capabilities. This is particularly important for cloud deployments where applications run across multiple instance types:

• AWS Graviton 2 (Neoverse N1): Baseline ARM64, no SVE/SVE2
• AWS Graviton 3 (Neoverse V1): 256-bit SVE, no SVE2
• AWS Graviton 4 (Neoverse V2): 128-bit SVE2
• GCP C4D (Neoverse V2): 128-bit SVE2

Currently, to leverage SVE2 optimizations, you must compile with -march=neoverse-v2 or similar flags, which produces binaries that won't run on older processors. This forces users to either:

1. Build multiple binaries for different targets
2. Build for the lowest common denominator and lose performance
3. Use separate container images for different instance types

This PR implements runtime CPU feature detection, similar to the existing BMI2 support on x86-64, allowing a single binary compiled for Neoverse N1 baseline (-mcpu=neoverse-n1) to automatically use SVE2 optimizations when available.

Changes

This PR adds runtime ARM SVE2 detection infrastructure:

Core Infrastructure

• CPU feature detection (lib/common/cpu.h): Platform-specific detection via getauxval() on Linux/Android, IsProcessorFeaturePresent() on Windows
• Build macros (lib/common/portability_macros.h): DYNAMIC_SVE2 macro to enable runtime dispatch
• Target attributes (lib/common/compiler.h): SVE2_TARGET_ATTRIBUTE for selective function compilation
• Context initialization (lib/compress/zstd_compress.c): Detect SVE2 once per compression context

Platform Support

• ✅ Linux/Android aarch64: Full runtime detection via getauxval()
• ✅ Windows on ARM: Full runtime detection via IsProcessorFeaturePresent()
• ❌ Apple platforms: Explicitly disabled (Apple Silicon doesn't support SVE/SVE2)

Recommended Flags

Benchmarking on Graviton 4:

# Compile for Neoverse N1 baseline with runtime SVE2 detection
make CC=gcc-15 CFLAGS="-O3 -mcpu=neoverse-n1"

# Binary automatically uses SVE2 on Graviton 4, falls back to baseline on Graviton 2/3

Overhead

Zero overhead on non-SVE2 systems:

• CPU detection happens once per compression context initialization
• No runtime checks in hot paths when SVE2 is unavailable
• Binary size increase is minimal

Related

This follows the same pattern as the existing x86-64 BMI2 runtime detection, extending it to ARM architectures.

See also:
#4440
#4429
#4418
#4414
#4413
#4411

[Andarwinux]

https://github.com/mingw-w64/mingw-w64/blob/55735d71ed1187098df4d80a8f6c98a7735b1cd5/mingw-w64-tools/widl/include/winnt.h#L1102-L1115

[iksaif]

Thanks @Andarwinux for pointing out the mingw-w64 header! I've updated the code in commit 1bf764f to use IsProcessorFeaturePresent() with PF_ARM_SVE_INSTRUCTIONS_AVAILABLE (46) and PF_ARM_SVE2_INSTRUCTIONS_AVAILABLE (47) for proper Windows ARM SVE/SVE2 detection.

[iksaif]

@Cyan4973 you might be interested as you previously worked on related SVE2 PRs

[terrelln]

@iksaif Generally seems reasonable, and we'll consider it for the next release, thanks for the PR!

Do you have benchmarks for the performance increase this brings on different ARM CPUs? We'll need to see improvements in benchmarks to merge this.

[iksaif]

@iksaif Generally seems reasonable, and we'll consider it for the next release, thanks for the PR!

Do you have benchmarks for the performance increase this brings on different ARM CPUs? We'll need to see improvements in benchmarks to merge this.

I think https://github.com/facebook/zstd/pulls?q=is%3Apr+SVE2+is%3Aclosed already have the details, but would you like me to show more ? (which particular CPU ?)