Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#74097 - [non-sequencer] Native CPU optimization mistakenly enabled
Attached to Project:
Community Packages
Opened by rvalue (rvalue) - Friday, 11 March 2022, 18:56 GMT
Last edited by David Runge (dvzrv) - Sunday, 13 March 2022, 11:13 GMT
Opened by rvalue (rvalue) - Friday, 11 March 2022, 18:56 GMT
Last edited by David Runge (dvzrv) - Sunday, 13 March 2022, 11:13 GMT
|
DetailsDescription:
Native CPU optimization is enabled by default during configuration since upstream commit#7c071c74, but not disabled in PKGBUILD file. This may cause problems if built with new CPUs with advanced ISA extensions like AVX-512. Additional info: Upstream commit: https://github.com/linuxaudio/non/commit/7c071c742211c3915d06176e41f1b1936abcc9be PKGBUILD code: https://github.com/archlinux/svntogit-community/blob/3912000f8c54baa9068c325310cb883245eda93d/trunk/PKGBUILD#L23 Suggested change: --- PKGBUILD +++ PKGBUILD @@ -20,7 +20,7 @@ build() { export LINKFLAGS="$LDFLAGS" CXXFLAGS+=" -std=c++14" - waf configure --prefix=/usr --project=sequencer + waf configure --prefix=/usr --project=sequencer --disable-native-cpu-optimization waf } |
This task depends upon
Closed by David Runge (dvzrv)
Sunday, 13 March 2022, 11:13 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with non-sequencer 1.10.0-2, non-{mixer,timeline} 1.3.0-4
Sunday, 13 March 2022, 11:13 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with non-sequencer 1.10.0-2, non-{mixer,timeline} 1.3.0-4
https://gist.github.com/r-value/daa67d57c2a21123f45e0c8926cdab26
I noticed this after packaging already, but am currently on the road and didn't have much time to investigate further.
The packages have indeed been built on our build server, which supports AVX512.
I will rebuild and disable the optmizations.