Your message dated Fri, 28 Nov 2025 09:04:53 +0100
with message-id <[email protected]>
and subject line Closing
has caused the Debian Bug report #983940,
regarding gf-complete: ftbfs with -march=x86-64-v3
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 [email protected]
immediately.)
--
983940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983940
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:gf-complete
Version: 1.0.2+2017.04.10.git.ea75cdf-3
Severity: minor
User: [email protected]
Usertags: ftbfs-x86-64-v3
Starting with LLVM 12 and GCC 11 (and backported to gcc-10 for Debian),
GCC introduces optimizations for new micro-architecture levels from
the x86-64 psABI. Filing these bug reports for packages building with
the current level (x86-64), but not with x86-64-v3.
To reproduce these issues, append -march=x86-64-v3 to the compiler
flags (CFLAGS, CXXFLAGS, ...). You also need hardware supporting these.
The easiest way is to call the dynamic linker in glibc 2.33 like
/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 --help
Otherwise look at the flags in /proc/cpuinfo and compare these with
those from table 3.1 in the System V Application Binary Interface doc:
https://gitlab.com/x86-psABIs/x86-64-ABI/-/wikis/x86-64-psABI
Please don't upload a package setting these flags by default. The
x86-64 baseline is still unchanged.
The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc10-v3/gf-complete_1.0.2+2017.04.10.git.ea75cdf-3_unstable_gcc10-v3.log
The last lines of the build log are at the end of this report.
[...]
libtool: link: gcc -O3 -msse -DINTEL_SSE -msse2 -DINTEL_SSE2 -msse3
-DINTEL_SSE3 -mssse3 -DINTEL_SSSE3 -mpclmul -DINTEL_SSE4_PCLMUL -msse4.1
-DINTEL_SSE4 -msse4.2 -DINTEL_SSE4 -fPIC -g -O2
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wl,-z -Wl,relro -o .libs/gf_example_4 gf_example_4.o
../src/.libs/libgf_complete.so
/bin/bash ../libtool --tag=CC --mode=link gcc -O3 -msse -DINTEL_SSE -msse2
-DINTEL_SSE2 -msse3 -DINTEL_SSE3 -mssse3 -DINTEL_SSSE3 -mpclmul
-DINTEL_SSE4_PCLMUL -msse4.1 -DINTEL_SSE4 -msse4.2 -DINTEL_SSE4 -fPIC -g -O2
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wl,-z,relro -o gf_example_6 gf_example_6.o
../src/libgf_complete.la
/bin/bash ../libtool --tag=CC --mode=link gcc -O3 -msse -DINTEL_SSE -msse2
-DINTEL_SSE2 -msse3 -DINTEL_SSE3 -mssse3 -DINTEL_SSSE3 -mpclmul
-DINTEL_SSE4_PCLMUL -msse4.1 -DINTEL_SSE4 -msse4.2 -DINTEL_SSE4 -fPIC -g -O2
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wl,-z,relro -o gf_example_7 gf_example_7.o
../src/libgf_complete.la
libtool: link: gcc -O3 -msse -DINTEL_SSE -msse2 -DINTEL_SSE2 -msse3
-DINTEL_SSE3 -mssse3 -DINTEL_SSSE3 -mpclmul -DINTEL_SSE4_PCLMUL -msse4.1
-DINTEL_SSE4 -msse4.2 -DINTEL_SSE4 -fPIC -g -O2
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wl,-z -Wl,relro -o .libs/gf_example_5 gf_example_5.o
../src/.libs/libgf_complete.so
libtool: link: gcc -O3 -msse -DINTEL_SSE -msse2 -DINTEL_SSE2 -msse3
-DINTEL_SSE3 -mssse3 -DINTEL_SSSE3 -mpclmul -DINTEL_SSE4_PCLMUL -msse4.1
-DINTEL_SSE4 -msse4.2 -DINTEL_SSE4 -fPIC -g -O2
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wl,-z -Wl,relro -o .libs/gf_example_6 gf_example_6.o
../src/.libs/libgf_complete.so
libtool: link: gcc -O3 -msse -DINTEL_SSE -msse2 -DINTEL_SSE2 -msse3
-DINTEL_SSE3 -mssse3 -DINTEL_SSSE3 -mpclmul -DINTEL_SSE4_PCLMUL -msse4.1
-DINTEL_SSE4 -msse4.2 -DINTEL_SSE4 -fPIC -g -O2
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wl,-z -Wl,relro -o .libs/gf_example_7 gf_example_7.o
../src/.libs/libgf_complete.so
make[2]: Leaving directory '/<<PKGBUILDDIR>>/examples'
make[2]: Entering directory '/<<PKGBUILDDIR>>'
make[2]: Nothing to be done for 'all-am'.
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
debian/rules override_dh_auto_test
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_auto_test
make -j4 check VERBOSE=1
make[2]: Entering directory '/<<PKGBUILDDIR>>'
Making check in src
make[3]: Entering directory '/<<PKGBUILDDIR>>/src'
make[3]: Nothing to be done for 'check'.
make[3]: Leaving directory '/<<PKGBUILDDIR>>/src'
Making check in tools
make[3]: Entering directory '/<<PKGBUILDDIR>>/tools'
make check-TESTS
make[4]: Entering directory '/<<PKGBUILDDIR>>/tools'
make[5]: Entering directory '/<<PKGBUILDDIR>>/tools'
./gf_methods 128 -A -U > gf_unit_w128.sh || rm gf_unit_w128.sh
./gf_methods 64 -A -U > gf_unit_w64.sh || rm gf_unit_w64.sh
./gf_methods 32 -A -U > gf_unit_w32.sh || rm gf_unit_w32.sh
./gf_methods 16 -A -U > gf_unit_w16.sh || rm gf_unit_w16.sh
./gf_methods 8 -A -U > gf_unit_w8.sh || rm gf_unit_w8.sh
./gf_methods 4 -A -U > gf_unit_w4.sh || rm gf_unit_w4.sh
PASS: gf_unit_w8.sh
PASS: gf_unit_w4.sh
PASS: gf_unit_w32.sh
PASS: gf_unit_w16.sh
PASS: gf_unit_w64.sh
PASS: gf_unit_w128.sh
============================================================================
Testsuite summary for gf-complete 1.0
============================================================================
# TOTAL: 6
# PASS: 6
# SKIP: 0
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
============================================================================
rm gf_unit_w4.sh gf_unit_w8.sh gf_unit_w128.sh gf_unit_w16.sh gf_unit_w32.sh
gf_unit_w64.sh
make[5]: Leaving directory '/<<PKGBUILDDIR>>/tools'
make[4]: Leaving directory '/<<PKGBUILDDIR>>/tools'
make[3]: Leaving directory '/<<PKGBUILDDIR>>/tools'
Making check in test
make[3]: Entering directory '/<<PKGBUILDDIR>>/test'
make[3]: Nothing to be done for 'check'.
make[3]: Leaving directory '/<<PKGBUILDDIR>>/test'
Making check in examples
make[3]: Entering directory '/<<PKGBUILDDIR>>/examples'
make[3]: Nothing to be done for 'check'.
make[3]: Leaving directory '/<<PKGBUILDDIR>>/examples'
make[3]: Entering directory '/<<PKGBUILDDIR>>'
make[3]: Nothing to be done for 'check-am'.
make[3]: Leaving directory '/<<PKGBUILDDIR>>'
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
./libtool --mode=execute qemu-x86_64-static -cpu
qemu64,-sse3,-ssse3,-sse4.1,-sse4.2 ./test/gf_unit 64 A -1 -
qemu: uncaught target signal 4 (Illegal instruction) - core dumped
make[1]: *** [debian/rules:21: override_dh_auto_test] Illegal instruction
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:10: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Hi,
As this bug is very old, and that GCC 11 (and above) where uploaded
without issues in this package (or maybe addressed, if I remember well),
I believe this bug can be closed.
Cheers,
Thomas Goirand (zigo)
--- End Message ---
