Bug#1003847: binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others)
On 2022-02-01 16:02, Tulio Magno Quites Machado Filho wrote: > Aurelien Jarno writes: > > > On 2022-01-19 22:08, John Paul Adrian Glaubitz wrote: > >> Hi Aurelien! > >> > >> Unfortunately, glibc no longer builds with this change on powerpc and ppc64 > >> and kernel builds still fails on both targets: > >> > >> > https://buildd.debian.org/status/fetch.php?pkg=glibc=powerpc=2.33-3=1642542048=0 > >> > https://buildd.debian.org/status/fetch.php?pkg=glibc=ppc64=2.33-3=1642542055=0 > > > > The ppc64el fix is not the cause for those failures. Previous glibc > > versions also do not build on powerpc and ppc64 following the binutils > > snapshot upload to sid. It's just that more code got broken on powerpc > > and ppc64 than on ppc64el. I have queued the backported fixes from > > upstream for the next upload. > > Are these issues happening when building glibc upstream too? No, upstream built fine, and same now for the 2.33 and 2.34 branches after I backported ee874f44fd55988808a4a162ef21bfa2cc8dc6f7. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#1003847: binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others)
Aurelien Jarno writes: > On 2022-01-19 22:08, John Paul Adrian Glaubitz wrote: >> Hi Aurelien! >> >> Unfortunately, glibc no longer builds with this change on powerpc and ppc64 >> and kernel builds still fails on both targets: >> >> > https://buildd.debian.org/status/fetch.php?pkg=glibc=powerpc=2.33-3=1642542048=0 >> > https://buildd.debian.org/status/fetch.php?pkg=glibc=ppc64=2.33-3=1642542055=0 > > The ppc64el fix is not the cause for those failures. Previous glibc > versions also do not build on powerpc and ppc64 following the binutils > snapshot upload to sid. It's just that more code got broken on powerpc > and ppc64 than on ppc64el. I have queued the backported fixes from > upstream for the next upload. Are these issues happening when building glibc upstream too? -- Tulio Magno
Bug#1003847: binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others)
Hi, On 2022-01-19 22:08, John Paul Adrian Glaubitz wrote: > Hi Aurelien! > > Unfortunately, glibc no longer builds with this change on powerpc and ppc64 > and kernel builds still fails on both targets: > > > https://buildd.debian.org/status/fetch.php?pkg=glibc=powerpc=2.33-3=1642542048=0 > > https://buildd.debian.org/status/fetch.php?pkg=glibc=ppc64=2.33-3=1642542055=0 The ppc64el fix is not the cause for those failures. Previous glibc versions also do not build on powerpc and ppc64 following the binutils snapshot upload to sid. It's just that more code got broken on powerpc and ppc64 than on ppc64el. I have queued the backported fixes from upstream for the next upload. > > https://buildd.debian.org/status/fetch.php?pkg=linux=powerpc=5.15.15-1=1642579068=0 > > https://buildd.debian.org/status/fetch.php?pkg=linux=ppc64=5.15.15-1=1642578946=0 Those failures are completely unrelated to do with glibc. A porter need to fix the kernel code to make it compatible with the new binutils. Cheers Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#1003847: binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others)
Hello! On 1/19/22 22:38, Jeffrey Walton wrote: > On Wed, Jan 19, 2022 at 4:08 PM John Paul Adrian Glaubitz > wrote: >> >> Unfortunately, glibc no longer builds with this change on powerpc and ppc64 >> and kernel builds still fails on both targets: >> >>> https://buildd.debian.org/status/fetch.php?pkg=glibc=powerpc=2.33-3=1642542048=0 >>> https://buildd.debian.org/status/fetch.php?pkg=glibc=ppc64=2.33-3=1642542055=0 >> >>> https://buildd.debian.org/status/fetch.php?pkg=linux=powerpc=5.15.15-1=1642579068=0 >>> https://buildd.debian.org/status/fetch.php?pkg=linux=ppc64=5.15.15-1=1642578946=0 > > This seems to be related to the ones stamped 1642542048 and 1642542055 > (the first two): > https://patchwork.sourceware.org/project/glibc/patch/20210925202746.819385-1...@us.ibm.com/ It will be fixed in glibc_2.33-4 [1] which has not been released yet. Adrian > [1] > https://salsa.debian.org/glibc-team/glibc/-/commit/20e02061f900515ebac6ee3872c5cd22ea5801d2 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1003847: binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others)
On Wed, Jan 19, 2022 at 4:08 PM John Paul Adrian Glaubitz wrote: > > Unfortunately, glibc no longer builds with this change on powerpc and ppc64 > and kernel builds still fails on both targets: > > > https://buildd.debian.org/status/fetch.php?pkg=glibc=powerpc=2.33-3=1642542048=0 > > https://buildd.debian.org/status/fetch.php?pkg=glibc=ppc64=2.33-3=1642542055=0 > > > https://buildd.debian.org/status/fetch.php?pkg=linux=powerpc=5.15.15-1=1642579068=0 > > https://buildd.debian.org/status/fetch.php?pkg=linux=ppc64=5.15.15-1=1642578946=0 This seems to be related to the ones stamped 1642542048 and 1642542055 (the first two): https://patchwork.sourceware.org/project/glibc/patch/20210925202746.819385-1...@us.ibm.com/
Bug#1003847: binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others)
Hi Aurelien! Unfortunately, glibc no longer builds with this change on powerpc and ppc64 and kernel builds still fails on both targets: > https://buildd.debian.org/status/fetch.php?pkg=glibc=powerpc=2.33-3=1642542048=0 > https://buildd.debian.org/status/fetch.php?pkg=glibc=ppc64=2.33-3=1642542055=0 > https://buildd.debian.org/status/fetch.php?pkg=linux=powerpc=5.15.15-1=1642579068=0 > https://buildd.debian.org/status/fetch.php?pkg=linux=ppc64=5.15.15-1=1642578946=0 Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Processed: Re: Bug#1003847: binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others)
Processing control commands: > reassign -1 glibc Bug #1003847 [src:binutils, src:glibc] binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others) Bug reassigned from package 'src:binutils, src:glibc' to 'glibc'. No longer marked as found in versions glibc/2.33-2 and binutils/2.37.50.20220106-2. Ignoring request to alter fixed versions of bug #1003847 to the same values previously set > found -1 glibc/2.29-1 Bug #1003847 [glibc] binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others) Marked as found in versions glibc/2.29-1. -- 1003847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003847: binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others)
control: reassign -1 glibc control: found -1 glibc/2.29-1 On 2022-01-16 21:15, Paul Gevers wrote: > Source: binutils, glibc > Control: found -1 binutils/2.37.50.20220106-2 > Control: found -1 glibc/2.33-2 > Severity: serious > Tags: sid bookworm > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: breaks needs-update > Control: affects -1 gcc-10 gcc-11 > > Dear maintainer(s), > > With a recent upload of binutils the autopkgtest of glibc fails in testing > when that autopkgtest is run with the binary packages of binutils from > unstable. It passes when run with only packages from testing. In tabular > form: > >passfail > binutils from testing2.37.50.20220106-2 > glibc from testing2.33-2 > all others from testingfrom testing > > I copied some of the output at the bottom of this report. > > Currently this regression is blocking the migration of binutils, gcc-10 and > gcc-11 to testing [1]. Due to the nature of this issue, I filed this bug > report against the binutils and glibc source packages. Can you please > investigate the situation and reassign the bug to the right package? Recent versions of binutils changed the way the .machine directive works on PowerPC. I have already backported a fix to our git. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc Description: PGP signature
Bug#1003847: binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others)
Source: binutils, glibc
Control: found -1 binutils/2.37.50.20220106-2
Control: found -1 glibc/2.33-2
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Control: affects -1 gcc-10 gcc-11
Dear maintainer(s),
With a recent upload of binutils the autopkgtest of glibc fails in
testing when that autopkgtest is run with the binary packages of
binutils from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
binutils from testing2.37.50.20220106-2
glibc from testing2.33-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of binutils, gcc-10
and gcc-11 to testing [1]. Due to the nature of this issue, I filed this
bug report against the binutils and glibc source packages. Can you
please investigate the situation and reassign the bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=binutils
https://ci.debian.net/data/autopkgtest/testing/ppc64el/g/glibc/18280958/log.gz
powerpc64le-linux-gnu-gcc-10
../sysdeps/ieee754/ldbl-128ibm/tst-strtold-ldbl-128ibm.c -c -std=gnu11
-fgnu89-inline -pipe -O2 -g
-fdebug-prefix-map=/tmp/autopkgtest-lxc.448kjxt6/downtmp/build.UW5/src=.
-mcpu=power8 -Wall -Wwrite-strings -Wundef -Werror -fmerge-all-constants
-frounding-math -fstack-protector-strong -Wstrict-prototypes
-Wold-style-definition -fmath-errno -mabi=ieeelongdouble -Wno-psabi
-mno-gnu-attribute -mlong-double-128 -mabi=ibmlongdouble
-isystem
/tmp/autopkgtest-lxc.448kjxt6/downtmp/build.UW5/src/debian/include
-I../include
-I/tmp/autopkgtest-lxc.448kjxt6/downtmp/build.UW5/src/build-tree/ppc64el-libc/stdlib
-I/tmp/autopkgtest-lxc.448kjxt6/downtmp/build.UW5/src/build-tree/ppc64el-libc
-I../sysdeps/unix/sysv/linux/powerpc/powerpc64/le/fpu
-I../sysdeps/unix/sysv/linux/powerpc/powerpc64/fpu
-I../sysdeps/unix/sysv/linux/powerpc/powerpc64/le
-I../sysdeps/unix/sysv/linux/powerpc/powerpc64
-I../sysdeps/unix/sysv/linux/wordsize-64
-I../sysdeps/unix/sysv/linux/powerpc -I../sysdeps/powerpc/nptl
-I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux
-I../sysdeps/nptl -I../sysdeps/pthread -I../sysdeps/gnu
-I../sysdeps/unix/inet -I../sysdeps/unix/sysv
-I../sysdeps/unix/powerpc -I../sysdeps/unix -I../sysdeps/posix
-I../sysdeps/powerpc/powerpc64/le/power8/fpu/multiarch
-I../sysdeps/powerpc/powerpc64/le/power7/fpu/multiarch
-I../sysdeps/powerpc/powerpc64/le/fpu/multiarch
-I../sysdeps/powerpc/powerpc64/le/power8/fpu
-I../sysdeps/powerpc/powerpc64/le/power7/fpu
-I../sysdeps/powerpc/powerpc64/le/fpu
-I../sysdeps/powerpc/powerpc64/fpu
-I../sysdeps/powerpc/powerpc64/le/power8/multiarch
-I../sysdeps/powerpc/powerpc64/le/power7/multiarch
-I../sysdeps/powerpc/powerpc64/le/multiarch
-I../sysdeps/powerpc/powerpc64/multiarch
-I../sysdeps/powerpc/powerpc64/le/power8
-I../sysdeps/powerpc/powerpc64/power8
-I../sysdeps/powerpc/powerpc64/le/power7
-I../sysdeps/powerpc/powerpc64/power7
-I../sysdeps/powerpc/powerpc64/power6
-I../sysdeps/powerpc/powerpc64/power4 -I../sysdeps/powerpc/power4
-I../sysdeps/powerpc/powerpc64/le -I../sysdeps/powerpc/powerpc64
-I../sysdeps/wordsize-64 -I../sysdeps/powerpc/fpu -I../sysdeps/powerpc
-I../sysdeps/ieee754/ldbl-128ibm-compat
-I../sysdeps/ieee754/ldbl-128ibm/include
-I../sysdeps/ieee754/ldbl-128ibm -I../sysdeps/ieee754/ldbl-opt
-I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32
-I../sysdeps/ieee754/float128 -I../sysdeps/ieee754
-I../sysdeps/generic -I.. -I../libio -I. -nostdinc -isystem
/usr/lib/gcc/powerpc64le-linux-gnu/10/include -isystem
/tmp/autopkgtest-lxc.448kjxt6/downtmp/build.UW5/src/debian/include
-D_LIBC_REENTRANT -include
/tmp/autopkgtest-lxc.448kjxt6/downtmp/build.UW5/src/build-tree/ppc64el-libc/libc-modules.h
-DMODULE_NAME=testsuite -include ../include/libc-symbols.h -DPIC
-DTOP_NAMESPACE=glibc -o
/tmp/autopkgtest-lxc.448kjxt6/downtmp/build.UW5/src/build-tree/ppc64el-libc/stdlib/tst-strtold-ldbl-128ibm.o
-MD -MP -MF
/tmp/autopkgtest-lxc.448kjxt6/downtmp/build.UW5/src/build-tree/ppc64el-libc/stdlib/tst-strtold-ldbl-128ibm.o.dt
-MT
/tmp/autopkgtest-lxc.448kjxt6/downtmp/build.UW5/src/build-tree/ppc64el-libc/stdlib/tst-strtold-ldbl-128ibm.o
{standard input}: Assembler messages:
{standard input}:78: Error: unrecognized opcode: `vspltisb'
{standard input}:79: Error: unrecognized opcode: `vspltisb'
{standard input}:80: Error: unrecognized opcode: `vpkuwus'
{standard input}:81: Error: unrecognized opcode: `mfvscr'
{standard input}:82: Error: unrecognized opcode: `stvx'
make[3]: ***
