Looked at potential performance regressions of removing AVX instructions.
(Updated the SRU template sections accordingly.)
The boinc packages do not provide high-performance code, it's the boinc
_applications_ written to be run by the client and linked against the
library for API access that have the high-performance code, IIUIC.
The API documentation/headers do not seem to provide any high-performance
functions (e.g., the crypto part are wrapper for openssl), the only code
it seems to implement is MD5.
Considering this change has been introduced in Debian ~2 years ago
(Feb-Jun 2022) and in Ubuntu Kinetic (22.10) and is still in place,
there indeed does not seem to be a performance regression (or other
issues related to it).
Looked at potential performance regressions of removing AVX instructions.
(Updated the SRU template sections accordingly.)
The boinc packages do not provide high-performance code, it's the boinc
_applications_ written to be run by the client and linked against the
library for API access that have the high-performance code, IIUIC.
The API documentation/ headers do not seem to provide any high-performance
functions (e.g., the crypto part are wrapper for openssl), the only code
it seems to implement is MD5.
https:/ /github. com/BOINC/ boinc/wiki/ ProjectMain# developing- boinc-applicati ons
Considering this change has been introduced in Debian ~2 years ago
(Feb-Jun 2022) and in Ubuntu Kinetic (22.10) and is still in place,
there indeed does not seem to be a performance regression (or other
issues related to it).
```
boinc (7.20.0+dfsg-1) unstable; urgency=medium
[ Steffen Moeller ]
* Reverse AVX instructions for better compatibility with older servers
```
https:/ /launchpad. net/ubuntu/ kinetic/ +source/ boinc