> Do you have any links to information about architecture baseline
support and
> -maes or -march=native?
Dear Maintainers,
This bug report and the related #1121104 can be resolved once a new
version is uploaded that includes the following build flag in debian/rules:
override_dh_auto_configure:
dh_auto_configure -- -DARCH=default -DNO_AES=ON
This corrects the baseline violations for amd64 caused by disabling
-march=native and the use of non-guaranteed AES-NI instructions. The
solution follows the precedent set by the monero package.
-march=native: non-portable binaries, compromising the base portability
of Debian...
https://salsa.debian.org/cryptocoin-team/feather-wallet/-/blob/master/monero/CMakeLists.txt?ref_type=heads#L733
-maes (AES-NI): uses non-guaranteed instructions on the amd64 baseline...
https://salsa.debian.org/cryptocoin-team/feather-wallet/-/blob/master/monero/CMakeLists.txt?ref_type=heads#L753-754
Implications:
* POSITIVE: The package will be fully portable and compliant with Debian
policies.
* NEGATIVE: There will be a performance penalty in operations using AES
encryption.
Following the specifications at:
https://wiki.debian.org/ArchitectureSpecificsMemo#amd64
Only mmx/sse/sse2 are guaranteed, explicitly excluding "sse3 and
higher". AES-NI instructions (enabled by -maes) are an extension of sse4
that is part of the x86-64-v3 level of psABI, not the base level
(x86-64-v1) required by Debian.
Best regards,
--
Manuel Guerra <[email protected]>
Debian Maintainer
4096 bit RSA key ECA5016D963F871E5873CFC2E573B97D48F2E520
keyserver: keyserver.ubuntu.com, keys.openpgp.org
