On 12/01/2025 20:36, Zbigniew Jędrzejewski-Szmek wrote:
I think any massive use of this scheme is unlikely. Note that we'd
want to this only for packages where the optimized code yields
noticeable benefits. There just aren't that many packages which do
significant number crunching_and_ don't already use some kind of
runtime cpu detection.
Most modern C/C++ applications that work with floating-point numbers can
get a boost by using modern CPU instructions. This speedup can be small
or significant, depending on the number of calculations.
I think such optimized binaries should go into a separate RPM packages
and should be handled by dnf depending on the running architecture. This
would solve both the disk space and latency issues.
Example: firefox-134.0-1.fc42.x86_64 vs firefox-134.0-1.fc42.x86_64-v2.
Since the number of these optimized packages will be small, I think it's
worth the CPU time to build them twice.
Benchmarks indicate 100–1000 μs.
1 second? I think it's too much.
--
Sincerely,
Vitaly Zaitsev (vitaly@xxxxxxxxxxxxxx)
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
