Control: reassign -1 src:freefem++
Control: severity -1 serious
Control: retitle -1 Baseline violation in i386 (-mmx -msse2) and amd64 (-mavx)
Control: found -1 3.47+dfsg1-1
On Sun, Mar 24, 2019 at 09:52:28PM +0100, Bernhard Übelacker wrote:
> Unfortunately I saw some bugs in the debian bug
As suggested, I rebuilt the debian package (version 3.61.1+dfsg1-4)
with and without adding --enable-generic to configure using a PC with
AVX support. I tested the resulting packages using 2 PCs without AVX
support. The package built with --enable-generic doesn't crash while
the other one always
Hello Bernhard and Dimitrios,
> I think the issue is that freefem++s configure activate
> AVX instructions when the build CPU supports it.
>
>
> I could reproduce the crash in a Buster amd64 qemu VM, that
> unintentionally did not support AVX (while the VM host would).
I reproduced the crash
Hello Dimitris, hello di dit,
I think the issue is that freefem++s configure activate
AVX instructions when the build CPU supports it.
I could reproduce the crash in a Buster amd64 qemu VM, that
unintentionally did not support AVX (while the VM host would).
That led to following backtrace:
> Both commands
>
> FreeFem++ a_tutorial.edp
>
> and
>
> FreeFem++-nw a_tutorial.edp
>
> work fine on an updated unstable/amd64 installation.
Indeed, it does not manifest on every computer as I wrote there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924009#10
Still I believe it is a
5 matches
Mail list logo
