Control: severity -1 important
On Wed, Aug 13, 2025 at 12:34:09AM +0100, Colin Watson wrote:
On Sat, May 31, 2025 at 12:48:55PM +1200, [email protected] wrote:
I've taken a look at the mimalloc-3.0.3 source. The setting
MI_OPT_ARCH=OFF in debian/rules appears to
invoke a falsehood if my interpretation of
mimalloc-3.0.3+ds/CMakeLists.txt is correct:
[...]
-march other than 'x86-64' should not be used if one intends to
generate universal x86-64 instructions:
<https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html>
I don't think this diagnosis can be the right one, because https://buildd.debian.org/status/fetch.php?pkg=mimalloc&arch=amd64&ver=3.0.3%2Bds-1&stamp=1743673297&raw=0
is verbose enough to show compiler command lines and they don't
include -march. Something else must be going on ...
I'm downgrading this for the moment as I can't currently find evidence
that it's a baseline violation. I've tried this in various ancient qemu
CPU models ("-cpu Conroe", "-cpu qemu64", "-cpu core2duo"), and it seems
fine there. I'm prepared to believe that I've missed something, but
figuring it out seems like a bit of a fishing expedition.
Adam, could you please give some details about your machine, and attach
your /proc/cpuinfo file? That might help narrow things down.
Thanks,
--
Colin Watson (he/him) [[email protected]]
