uucore: only probe hardware features the target can have

[xtqqczze]

No description provided.

[codspeed]

Merging this PR will degrade performance by 14.55%

⚠️ 116 benchmarks spent significant time in system calls

System calls cannot be consistently instrumented, so they are not included in the measure, which understates the real cost. Please switch to the Walltime instrument to accurately measure system calls.

Measurement and system calls

• sort_unique_utf8_locale
• du_all_wide_tree[(5000, 500)]
• cksum_default
• dd_copy_partial
• dd_copy_8k_blocks
• du_deep_tree[(100, 3)]
• wc_bytes_synthetic[500]
• cksum_sysv
• wc_bytes_synthetic[1]
• cut_fields_newline_delim
• …and 106 more

ℹ️ 1 benchmark has no flame graph

The flamegraph could not be generated because too much time was spent in runtime internals, making the visualization not useful for performance analysis.

• sort_dictionary_order[500000]

❌ 2 regressed benchmarks
✅ 399 untouched benchmarks
⏩ 70 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	factor_three_39_bit_primes	567 ms	748.6 ms	-24.26%
❌	Simulation	factor_thirteen_39_bit_primes	9.5 s	9.8 s	-3.6%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing xtqqczze:uucore-hardware (ab2c824) with main (7654e67)}

Footnotes

1. 70 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[github-actions]

GNU testsuite comparison:

Skipping an intermittent issue tests/date/resolution (passes in this run but fails in the 'main' branch)