Your message dated Mon, 20 Feb 2023 00:07:20 +0100
with message-id <dd182e52492d2220f7348dd108943...@debian.org>
and subject line Re: xtensor: baseline violation: builds with -march=native
has caused the Debian Bug report #1030775,
regarding xtensor: baseline violation: builds with -march=native
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1030775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xtensor
Version: 0.24.3-1
Severity: serious
xtensor build with -march=native, thus the resulting binaries depend on
the buildd being used and may not work on older hardware.
In the worst case a future stable security update built on then modern
hardware will render the binaries unusable elsewhere.
Andreas
--- End Message ---
--- Begin Message ---
Control: tags 1030775 - moreinfo
Header-only package, -march=native is only used in tests, so no bug
here.
-march=native is made accessible via xtensor cmake config files, but
again that is not used automatically.
It is added to the flags for the xtensor::optimize target, but that
needs to be explicitly specified by client program (in a
target_link_libraries() directive) or else is ignored. See
https://xtensor.readthedocs.io/en/latest/build-options.html#build-and-optimization
. So again, this optimized build doesn't get built into debian binary
packages.
Hence we can close this bug.
--- End Message ---
