* The 2.40 branch has been created
@ 2022-12-31 13:00 Nick Clifton
2023-01-02 11:41 ` Matthias Klose
2023-01-04 3:05 ` Alan Modra
0 siblings, 2 replies; 15+ messages in thread
From: Nick Clifton @ 2022-12-31 13:00 UTC (permalink / raw)
To: binutils
Hi Everyone,
The 2.40 branch has now been created:
git clone git://sourceware.org/git/binutils-gdb.git -b binutils-2_40-branch
A snapshot of the sources is also available here:
https://sourceware.org/pub/binutils/snapshots/binutils-2.39.90.tar.xz
Please could all patches for the branch be run by me.
The rules for the branch are:
* No new features.
* Target specific bug fixes are OK.
* Generic bug fixes are OK if they are important and widely tested.
* Documentation updates/fixes are OK.
* Translation updates are OK.
* Fixes for testsuite failures are OK.
Ideally I would like to make the release happen in two weeks time,
i.e. Jan 14, 2023. Which I hope will be enough time for everyone
to get their final fixes in.
Cheers
Nick
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: The 2.40 branch has been created 2022-12-31 13:00 The 2.40 branch has been created Nick Clifton @ 2023-01-02 11:41 ` Matthias Klose 2023-01-02 11:56 ` Matthias Klose ` (3 more replies) 2023-01-04 3:05 ` Alan Modra 1 sibling, 4 replies; 15+ messages in thread From: Matthias Klose @ 2023-01-02 11:41 UTC (permalink / raw) To: Nick Clifton, binutils On 31.12.22 14:00, Nick Clifton via Binutils wrote: > Hi Everyone, > > The 2.40 branch has now been created: > > git clone git://sourceware.org/git/binutils-gdb.git -b binutils-2_40-branch > > A snapshot of the sources is also available here: > > https://sourceware.org/pub/binutils/snapshots/binutils-2.39.90.tar.xz > > Please could all patches for the branch be run by me. > The rules for the branch are: > > * No new features. > * Target specific bug fixes are OK. > * Generic bug fixes are OK if they are important and widely tested. > * Documentation updates/fixes are OK. > * Translation updates are OK. > * Fixes for testsuite failures are OK. > > Ideally I would like to make the release happen in two weeks time, > i.e. Jan 14, 2023. Which I hope will be enough time for everyone > to get their final fixes in. No test failures on amd64, ppc64el, ppc64. No test results yet for alpha, m68k, sh4, the hurd and KFreeBSD. For riscv64, there also is PR29940. Looks like libbacktrace is not built at build time, but only at test time when running make check. aarch64-linux-gnu: Running /<<PKGBUILDDIR>>/ld/testsuite/ld-aarch64/aarch64-elf.exp ... FAIL: ld-aarch64/tls-relax-gdesc-le-now arm-linux-gnueabi: Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/tls.exp ... FAIL: Build pr22263-1 Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ifunc/ifunc.exp ... FAIL: Run pr18841 with libpr18841b.so FAIL: Run pr18841 with libpr18841c.so FAIL: Run pr18841 with libpr18841bn.so (-z now) FAIL: Run pr18841 with libpr18841cn.so (-z now) FAIL: Run pr23169a FAIL: Run pr23169d arm-linux-gnueabihf: Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ifunc/ifunc.exp ... FAIL: Run pr18841 with libpr18841b.so FAIL: Run pr18841 with libpr18841c.so FAIL: Run pr18841 with libpr18841bn.so (-z now) FAIL: Run pr18841 with libpr18841cn.so (-z now) FAIL: Run pr23169a FAIL: Run pr23169d i686-linux-gnu: Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ctf/ctf.exp ... FAIL: Diagnostics - No parent dictionary Running /<<PKGBUILDDIR>>/ld/testsuite/ld-i386/i386.exp ... FAIL: Run pr19031 FAIL: Run got1 FAIL: Undefined weak symbol (-fPIE -no-pie) FAIL: Undefined weak symbol (-fPIE -pie) mipsel-linux-gnu (gas and ld): Running /<<PKGBUILDDIR>>/gas/testsuite/gas/mips/mips.exp ... FAIL: MIPS RM7000 workarounds test 2 (mips3) FAIL: MIPS RM7000 workarounds test 2 (mips4) FAIL: MIPS RM7000 workarounds test 2 (mips5) FAIL: MIPS RM7000 workarounds test 2 (mips64) FAIL: MIPS RM7000 workarounds test 2 (mips64r2) FAIL: MIPS RM7000 workarounds test 2 (mips64r3) FAIL: MIPS RM7000 workarounds test 2 (mips64r5) FAIL: MIPS RM7000 workarounds test 2 (octeon) FAIL: MIPS RM7000 workarounds test 2 (octeon2) FAIL: MIPS RM7000 workarounds test 2 (octeon3) FAIL: MIPS RM7000 workarounds test 2 (octeonp) FAIL: MIPS RM7000 workarounds test 2 (r4000) FAIL: MIPS RM7000 workarounds test 2 (sb1) FAIL: MIPS RM7000 workarounds test 2 (vr5400) FAIL: MIPS RM7000 workarounds test 2 (xlr) FAIL: MIPS II load $zero (interaptiv-mr2) FAIL: MIPS II load $zero (mips2) FAIL: MIPS II load $zero (mips3) FAIL: MIPS II load $zero (mips4) FAIL: MIPS II load $zero (mips5) FAIL: MIPS II load $zero (mips32) FAIL: MIPS II load $zero (mips32r2) FAIL: MIPS II load $zero (mips32r3) FAIL: MIPS II load $zero (mips32r5) FAIL: MIPS II load $zero (mips32r6) FAIL: MIPS II load $zero (mips64) FAIL: MIPS II load $zero (mips64r2) FAIL: MIPS II load $zero (mips64r3) FAIL: MIPS II load $zero (mips64r5) FAIL: MIPS II load $zero (mips64r6) FAIL: MIPS II load $zero (octeon) FAIL: MIPS II load $zero (octeon2) FAIL: MIPS II load $zero (octeon3) FAIL: MIPS II load $zero (octeonp) FAIL: MIPS II load $zero (r4000) FAIL: MIPS II load $zero (sb1) FAIL: MIPS II load $zero (vr5400) FAIL: MIPS II load $zero (xlr) FAIL: MIPS III load $zero (mips3) FAIL: MIPS III load $zero (mips4) FAIL: MIPS III load $zero (mips5) FAIL: MIPS III load $zero (mips64) FAIL: MIPS III load $zero (mips64r2) FAIL: MIPS III load $zero (mips64r3) FAIL: MIPS III load $zero (mips64r5) FAIL: MIPS III load $zero (mips64r6) FAIL: MIPS III load $zero (octeon) FAIL: MIPS III load $zero (octeon2) FAIL: MIPS III load $zero (octeon3) FAIL: MIPS III load $zero (octeonp) FAIL: MIPS III load $zero (r4000) FAIL: MIPS III load $zero (sb1) FAIL: MIPS III load $zero (vr5400) FAIL: MIPS III load $zero (xlr) FAIL: MIPS ELF reloc 28 (LLD/SCD, n32) FAIL: MIPS ELF reloc 28 (LLD/SCD, n64) FAIL: Full MIPS R5900 FAIL: MIPS MIPSR6 instructions (mips32r6) FAIL: MIPS MIPSR6 instructions (mips64r6) FAIL: MIPS MIPSR6 instructions (mips64r6) FAIL: MIPS MIPSR6 instructions (mips64r6) FAIL: MIPS64r6 n32 instructions (mips64r6) FAIL: MIPS64r6 n64 instructions (mips64r6) Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/indirect.exp ... FAIL: Run indirect5 1 FAIL: Run indirect5 2 FAIL: Run indirect6 1 FAIL: Run indirect6 2 FAIL: indirect5a dynsym FAIL: indirect5b dynsym FAIL: indirect6a dynsym FAIL: indirect6b dynsym FAIL: Run indirect5 3 FAIL: Run indirect5 4 FAIL: Run indirect6 3 FAIL: Run indirect6 4 FAIL: indirect5c dynsym FAIL: indirect5d dynsym FAIL: indirect6c dynsym FAIL: indirect6d dynsym Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/shared.exp ... FAIL: Build libpr16496b.so FAIL: Run pr2404 FAIL: Run pr2404n FAIL: Run pr2404 with PIE FAIL: Run pr2404 with PIE (-z now) FAIL: Run pr21964-4 Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elfvers/vers.exp ... FAIL: vers24a FAIL: vers24b FAIL: vers24c Running /<<PKGBUILDDIR>>/ld/testsuite/ld-gc/gc.exp ... FAIL: --gc-sections with --defsym FAIL: --gc-sections with KEEP FAIL: --gc-sections with __start_SECTIONNAME Running /<<PKGBUILDDIR>>/ld/testsuite/ld-plugin/lto.exp ... FAIL: PR ld/12982 FAIL: ld-plugin/lto-3r FAIL: ld-plugin/lto-5r FAIL: PR ld/19317 (2) FAIL: PR ld/15323 (4) FAIL: PR ld/19317 (3) Running /<<PKGBUILDDIR>>/ld/testsuite/ld-plugin/plugin.exp ... FAIL: plugin claimfile lost symbol FAIL: plugin claimfile replace symbol FAIL: plugin claimfile resolve symbol FAIL: plugin claimfile lost symbol with source FAIL: plugin claimfile replace symbol with source FAIL: plugin claimfile resolve symbol with source FAIL: plugin 2 with source lib FAIL: load plugin 2 with source FAIL: plugin 3 with source lib FAIL: load plugin 3 with source Running /<<PKGBUILDDIR>>/ld/testsuite/ld-shared/shared.exp ... FAIL: shared (non PIC) FAIL: shared (PIC main, non PIC so) s390x-linux-gnu: Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/shared.exp ... FAIL: pr26580-3 FAIL: Run pr21964-4 ia64-linux-gnu: Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ctf/ctf.exp ... FAIL: Arrays (conflicted) FAIL: Conflicted data syms, partially indexed, stripped, with variables FAIL: Conflicted data syms, partially indexed, stripped FAIL: Nonrepresentable types Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/elf.exp ... FAIL: PR ld/22269 FAIL: PR ld/22269 (-z dynamic-undefined-weak) FAIL: Build pr26391-5.o FAIL: Build pr26391-6.o FAIL: Run pr26391-5 FAIL: Run pr26391-6 Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/indirect.exp ... FAIL: Run with libpr18720c.so 1 FAIL: Run with libpr18720c.so 2 FAIL: Run with libpr18720c.so 3 FAIL: Run with libpr18720c.so 4 FAIL: Run with libpr18720c.so 5 Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/shared.exp ... FAIL: DT_TEXTREL map file warning FAIL: pr22269-1 (static pie undefined weak) FAIL: Run pr18718 FAIL: Run pr18718 (-z now) FAIL: Run pr18718 with PIE (1) FAIL: Run pr18718 with PIE (2) FAIL: Run pr18718 with PIE (3) FAIL: Run pr18718 with PIE (4) FAIL: Run pr18718 with PIC (1) FAIL: Run pr18718 with PIC (2) FAIL: Run pr18718 with PIC (3) FAIL: Run pr18718 with PIC (4) FAIL: Build pr23162a FAIL: Build pr23162b FAIL: Build libpr23161a.so FAIL: Build pr23161a FAIL: Build libpr23161b.so FAIL: Build pr23161b Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/tls.exp ... FAIL: Build pr22263-1 Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ifunc/ifunc.exp ... FAIL: ifunc-using shared library does not contain R_*_IRELATIVE relocation FAIL: Local ifunc-using executable does not contain R_*_IRELATIVE relocation FAIL: Static ifunc-using executable does not contain R_*_IRELATIVE relocation powerpc-linux-gnu: Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ctf/ctf.exp ... FAIL: Diagnostics - No parent dictionary riscv64-linux-gnu: Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/shared.exp ... FAIL: Run pr21964-4 Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/tls.exp ... FAIL: Build pr22263-1 sparc64-linux-gnu: Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/elf.exp ... FAIL: Run pr26391-5 FAIL: Run pr26391-6 x86_64-linux-gnux32: Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ctf/ctf.exp ... FAIL: Diagnostics - No parent dictionary ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: The 2.40 branch has been created 2023-01-02 11:41 ` Matthias Klose @ 2023-01-02 11:56 ` Matthias Klose 2023-01-02 12:03 ` Andreas Schwab ` (2 subsequent siblings) 3 siblings, 0 replies; 15+ messages in thread From: Matthias Klose @ 2023-01-02 11:56 UTC (permalink / raw) To: Nick Clifton, binutils; +Cc: debian-mips On 02.01.23 12:41, Matthias Klose wrote: > On 31.12.22 14:00, Nick Clifton via Binutils wrote: >> Hi Everyone, >> >> The 2.40 branch has now been created: >> >> git clone git://sourceware.org/git/binutils-gdb.git -b binutils-2_40-branch >> >> A snapshot of the sources is also available here: >> >> https://sourceware.org/pub/binutils/snapshots/binutils-2.39.90.tar.xz >> >> Please could all patches for the branch be run by me. >> The rules for the branch are: >> >> * No new features. >> * Target specific bug fixes are OK. >> * Generic bug fixes are OK if they are important and widely tested. >> * Documentation updates/fixes are OK. >> * Translation updates are OK. >> * Fixes for testsuite failures are OK. >> >> Ideally I would like to make the release happen in two weeks time, >> i.e. Jan 14, 2023. Which I hope will be enough time for everyone >> to get their final fixes in. > > No test failures on amd64, ppc64el, ppc64. > > No test results yet for alpha, m68k, sh4, the hurd and KFreeBSD. > > For riscv64, there also is PR29940. > > Looks like libbacktrace is not built at build time, but only at test time when > running make check. mips64el-linux-gnu: Running /<<PKGBUILDDIR>>/gas/testsuite/gas/all/gas.exp ... FAIL: forward expression FAIL: assignment tests FAIL: gas/all/none Running /<<PKGBUILDDIR>>/gas/testsuite/gas/elf/elf.exp ... FAIL: gas/elf/missing-build-notes Running /<<PKGBUILDDIR>>/gas/testsuite/gas/macros/macros.exp ... FAIL: macro test 2 FAIL: macro irp FAIL: macro rept FAIL: nested irp/irpc/rept FAIL: macro vararg Running /<<PKGBUILDDIR>>/gas/testsuite/gas/mips/mips.exp ... FAIL: Compact EH EB #1 with personality ID and FDE data FAIL: Compact EH EB #2 with personality routine and FDE data FAIL: Compact EH EB #3 with personality id and large FDE data FAIL: Compact EH EB #4 with personality id, FDE data and LSDA FAIL: Compact EH EB #5 with personality routine, FDE data and LSDA FAIL: Compact EH EB #6 with personality id, LSDA and large FDE data FAIL: Compact EH EB #7 with personality id and fallback FDE FAIL: Compact EH EL #1 with personality ID and FDE data FAIL: Compact EH EL #2 with personality routine and FDE data FAIL: Compact EH EL #3 with personality id and large FDE data FAIL: Compact EH EL #4 with personality id, FDE data and LSDA FAIL: Compact EH EL #5 with personality routine, FDE data and LSDA FAIL: Compact EH EL #6 with personality id, LSDA and large FDE data FAIL: Compact EH EL #7 with personality id and fallback FDE FAIL: MIPS RM7000 workarounds test 2 (micromips) FAIL: MIPS RM7000 workarounds test 2 (mips3) FAIL: MIPS RM7000 workarounds test 2 (mips4) FAIL: MIPS RM7000 workarounds test 2 (mips5) FAIL: MIPS RM7000 workarounds test 2 (mips64) FAIL: MIPS RM7000 workarounds test 2 (mips64r2) FAIL: MIPS RM7000 workarounds test 2 (mips64r3) FAIL: MIPS RM7000 workarounds test 2 (mips64r5) FAIL: MIPS RM7000 workarounds test 2 (octeon) FAIL: MIPS RM7000 workarounds test 2 (octeon2) FAIL: MIPS RM7000 workarounds test 2 (octeon3) FAIL: MIPS RM7000 workarounds test 2 (octeonp) FAIL: MIPS RM7000 workarounds test 2 (r4000) FAIL: MIPS RM7000 workarounds test 2 (sb1) FAIL: MIPS RM7000 workarounds test 2 (vr5400) FAIL: MIPS RM7000 workarounds test 2 (xlr) FAIL: MIPS II load $zero (interaptiv-mr2) FAIL: MIPS II load $zero (mips2) FAIL: MIPS II load $zero (mips3) FAIL: MIPS II load $zero (mips4) FAIL: MIPS II load $zero (mips5) FAIL: MIPS II load $zero (mips32) FAIL: MIPS II load $zero (mips32r2) FAIL: MIPS II load $zero (mips32r3) FAIL: MIPS II load $zero (mips32r5) FAIL: MIPS II load $zero (mips32r6) FAIL: MIPS II load $zero (mips64) FAIL: MIPS II load $zero (mips64r2) FAIL: MIPS II load $zero (mips64r3) FAIL: MIPS II load $zero (mips64r5) FAIL: MIPS II load $zero (mips64r6) FAIL: MIPS II load $zero (octeon) FAIL: MIPS II load $zero (octeon2) FAIL: MIPS II load $zero (octeon3) FAIL: MIPS II load $zero (octeonp) FAIL: MIPS II load $zero (r4000) FAIL: MIPS II load $zero (sb1) FAIL: MIPS II load $zero (vr5400) FAIL: MIPS II load $zero (xlr) FAIL: MIPS III load $zero (mips3) FAIL: MIPS III load $zero (mips4) FAIL: MIPS III load $zero (mips5) FAIL: MIPS III load $zero (mips64) FAIL: MIPS III load $zero (mips64r2) FAIL: MIPS III load $zero (mips64r3) FAIL: MIPS III load $zero (mips64r5) FAIL: MIPS III load $zero (mips64r6) FAIL: MIPS III load $zero (octeon) FAIL: MIPS III load $zero (octeon2) FAIL: MIPS III load $zero (octeon3) FAIL: MIPS III load $zero (octeonp) FAIL: MIPS III load $zero (r4000) FAIL: MIPS III load $zero (sb1) FAIL: MIPS III load $zero (vr5400) FAIL: MIPS III load $zero (xlr) FAIL: mips jalx FAIL: .set arch=FOO FAIL: MIPS ELF reloc 28 (LLD/SCD, n32) FAIL: MIPS ELF reloc 28 (LLD/SCD, n64) FAIL: ST Microelectronics Loongson-2F workarounds of nop issue FAIL: ST Microelectronics Loongson-2F workarounds of Jump Instruction issue FAIL: MIPS-OCTEON octeon_saa_saad (octeon2) FAIL: MIPS-OCTEON octeon_saa_saad (octeon3) FAIL: MIPS-OCTEON octeon_saa_saad (octeonp) FAIL: MIPS DSP ASE for MIPS64 FAIL: gas/mips/align2 FAIL: gas/mips/align2-el FAIL: Full MIPS R5900 FAIL: MIPS R5900 VU0 FAIL: Locally-resolvable PC-relative code references FAIL: MIPS MIPSR6 instructions (mips32r6) FAIL: MIPS MIPSR6 instructions (mips64r6) FAIL: MIPS MIPSR6 instructions (mips64r6) FAIL: MIPS MIPSR6 instructions (mips64r6) FAIL: MIPS64r6 n32 instructions (mips64r6) FAIL: MIPS64r6 n64 instructions (mips64r6) FAIL: Paired LL/SC for mips64r6 (mips64r6) ld: Running /<<PKGBUILDDIR>>/ld/testsuite/ld-bootstrap/bootstrap.exp ... FAIL: bootstrap FAIL: bootstrap with strip FAIL: bootstrap with -Wl,--traditional-format FAIL: bootstrap with -Wl,--no-keep-memory FAIL: bootstrap with -Wl,--relax FAIL: bootstrap with -Wl,--max-cache-size=-1 Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/elf.exp ... FAIL: ld-elf/eh5 FAIL: ld-elf/group3a FAIL: ld-elf/group3b FAIL: Place orphan sections (map file check) FAIL: ld-elf/orphan-region FAIL: ld-elf/orphan Running /<<PKGBUILDDIR>>/ld/testsuite/ld-mips-elf/mips-elf.exp ... FAIL: MIPS16 link PC-relative operations 0 (n32) FAIL: MIPS16 link PC-relative operations 1 (n32) FAIL: MIPS16e2 link PC-relative operations 0 (n32) FAIL: MIPS16e2 link PC-relative operations 1 (n32) FAIL: MIPS jalx-1 FAIL: MIPS JALX to unaligned symbol with addend 0 FAIL: MIPS JALX to unaligned symbol with addend 2 FAIL: MIPS16 JALX to unaligned symbol with addend 0 FAIL: microMIPS JALX to unaligned symbol with addend 0 FAIL: ld-mips-elf/no-shared-1-n32 FAIL: ld-mips-elf/pie-n32 FAIL: MIPS ELF got reloc n32 FAIL: MIPS ELF xgot reloc n32 FAIL: MIPS relax-jalr n32 FAIL: MIPS rel32 n32 FAIL: _gp scope test (n32 shared library) FAIL: _gp scope test (n32 versioned library) FAIL: _gp scope test (n32 executable) FAIL: ld-mips-elf/reloc-1-n32 FAIL: MIPS eh-frame 1, n32 FAIL: MIPS eh-frame 2, n32 FAIL: MIPS Compact EH 6 FAIL: JAL overflow 2 FAIL: MIPS textrel-1 FAIL: GOT page test 3 FAIL: GOT page 5 FAIL: GOT page 6 FAIL: GOT page 7 (order 1) FAIL: GOT page 7 (order 2) FAIL: GOT dump (readelf -A) test 1 FAIL: MIPS reloc estimation 1 FAIL: Emit relocs 1 FAIL: MIPS16 interlinking for local functions 1 FAIL: ld-mips-elf/attr-gnu-4-10 FAIL: ld-mips-elf/attr-gnu-4-0-n32-ph FAIL: ld-mips-elf/attr-gnu-4-1-n32-ph FAIL: ld-mips-elf/attr-gnu-4-2-n32-ph FAIL: ld-mips-elf/attr-gnu-4-3-n32-ph FAIL: MIPS export class call relocation test (n32) FAIL: n32 PLTs for mixed MIPS and MIPS16 FAIL: n32 PLTs for mixed MIPS and microMIPS FAIL: PR ld/21375 in shared library (n32) FAIL: PR ld/21375 in shared library (n32, hidden) FAIL: PR ld/21375 in shared library (n32, microMIPS) FAIL: PR ld/21375 in shared library (n32, microMIPS, hidden) FAIL: MIPS global/local symbol table split (n32) FAIL: MIPS symbol table sort and section symbol names (relocatable) (n32) FAIL: MIPS symbol table sort and section symbol names (fully linked) (n32) Running /<<PKGBUILDDIR>>/ld/testsuite/ld-scripts/overlay-size.exp ... FAIL: overlay size (map file check) FAIL: overlay size Running /<<PKGBUILDDIR>>/ld/testsuite/ld-undefined/undefined.exp ... FAIL: undefined symbols in shared lib (dyn reloc) ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: The 2.40 branch has been created 2023-01-02 11:41 ` Matthias Klose 2023-01-02 11:56 ` Matthias Klose @ 2023-01-02 12:03 ` Andreas Schwab 2023-01-02 15:59 ` Christophe Lyon 2023-01-04 12:16 ` Nick Alcock 3 siblings, 0 replies; 15+ messages in thread From: Andreas Schwab @ 2023-01-02 12:03 UTC (permalink / raw) To: Matthias Klose via Binutils; +Cc: Nick Clifton, Matthias Klose On Jan 02 2023, Matthias Klose via Binutils wrote: > Looks like libbacktrace is not built at build time, but only at test time > when running make check. libbacktrace is not part of the binutils release. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different." ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: The 2.40 branch has been created 2023-01-02 11:41 ` Matthias Klose 2023-01-02 11:56 ` Matthias Klose 2023-01-02 12:03 ` Andreas Schwab @ 2023-01-02 15:59 ` Christophe Lyon 2023-01-02 23:05 ` Mark Wielaard 2023-01-09 16:00 ` Christophe Lyon 2023-01-04 12:16 ` Nick Alcock 3 siblings, 2 replies; 15+ messages in thread From: Christophe Lyon @ 2023-01-02 15:59 UTC (permalink / raw) To: Matthias Klose, Nick Clifton, binutils Hi Matthias! On 1/2/23 12:41, Matthias Klose via Binutils wrote: > On 31.12.22 14:00, Nick Clifton via Binutils wrote: >> Hi Everyone, >> >> The 2.40 branch has now been created: >> >> git clone git://sourceware.org/git/binutils-gdb.git -b >> binutils-2_40-branch >> >> A snapshot of the sources is also available here: >> >> >> https://sourceware.org/pub/binutils/snapshots/binutils-2.39.90.tar.xz >> >> Please could all patches for the branch be run by me. >> The rules for the branch are: >> >> * No new features. >> * Target specific bug fixes are OK. >> * Generic bug fixes are OK if they are important and widely tested. >> * Documentation updates/fixes are OK. >> * Translation updates are OK. >> * Fixes for testsuite failures are OK. >> >> Ideally I would like to make the release happen in two weeks time, >> i.e. Jan 14, 2023. Which I hope will be enough time for everyone >> to get their final fixes in. > > No test failures on amd64, ppc64el, ppc64. > > No test results yet for alpha, m68k, sh4, the hurd and KFreeBSD. > > For riscv64, there also is PR29940. > > Looks like libbacktrace is not built at build time, but only at test > time when running make check. > > > aarch64-linux-gnu: > > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-aarch64/aarch64-elf.exp ... > FAIL: ld-aarch64/tls-relax-gdesc-le-now > > > arm-linux-gnueabi: > > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/tls.exp ... > FAIL: Build pr22263-1 > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ifunc/ifunc.exp ... > FAIL: Run pr18841 with libpr18841b.so > FAIL: Run pr18841 with libpr18841c.so > FAIL: Run pr18841 with libpr18841bn.so (-z now) > FAIL: Run pr18841 with libpr18841cn.so (-z now) > FAIL: Run pr23169a > FAIL: Run pr23169d > > > arm-linux-gnueabihf: > > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ifunc/ifunc.exp ... > FAIL: Run pr18841 with libpr18841b.so > FAIL: Run pr18841 with libpr18841c.so > FAIL: Run pr18841 with libpr18841bn.so (-z now) > FAIL: Run pr18841 with libpr18841cn.so (-z now) I have reproduced these errors and I have a simple fix I hope to post shortly. Thanks for catching this, I've just realized that Sourceware's buildbot only runs a subset of binutils tests, which explains why this wasn't noticed before. Christophe > FAIL: Run pr23169a > FAIL: Run pr23169d > > i686-linux-gnu: > > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ctf/ctf.exp ... > FAIL: Diagnostics - No parent dictionary > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-i386/i386.exp ... > FAIL: Run pr19031 > FAIL: Run got1 > FAIL: Undefined weak symbol (-fPIE -no-pie) > FAIL: Undefined weak symbol (-fPIE -pie) > > > mipsel-linux-gnu (gas and ld): > > Running /<<PKGBUILDDIR>>/gas/testsuite/gas/mips/mips.exp ... > FAIL: MIPS RM7000 workarounds test 2 (mips3) > FAIL: MIPS RM7000 workarounds test 2 (mips4) > FAIL: MIPS RM7000 workarounds test 2 (mips5) > FAIL: MIPS RM7000 workarounds test 2 (mips64) > FAIL: MIPS RM7000 workarounds test 2 (mips64r2) > FAIL: MIPS RM7000 workarounds test 2 (mips64r3) > FAIL: MIPS RM7000 workarounds test 2 (mips64r5) > FAIL: MIPS RM7000 workarounds test 2 (octeon) > FAIL: MIPS RM7000 workarounds test 2 (octeon2) > FAIL: MIPS RM7000 workarounds test 2 (octeon3) > FAIL: MIPS RM7000 workarounds test 2 (octeonp) > FAIL: MIPS RM7000 workarounds test 2 (r4000) > FAIL: MIPS RM7000 workarounds test 2 (sb1) > FAIL: MIPS RM7000 workarounds test 2 (vr5400) > FAIL: MIPS RM7000 workarounds test 2 (xlr) > FAIL: MIPS II load $zero (interaptiv-mr2) > FAIL: MIPS II load $zero (mips2) > FAIL: MIPS II load $zero (mips3) > FAIL: MIPS II load $zero (mips4) > FAIL: MIPS II load $zero (mips5) > FAIL: MIPS II load $zero (mips32) > FAIL: MIPS II load $zero (mips32r2) > FAIL: MIPS II load $zero (mips32r3) > FAIL: MIPS II load $zero (mips32r5) > FAIL: MIPS II load $zero (mips32r6) > FAIL: MIPS II load $zero (mips64) > FAIL: MIPS II load $zero (mips64r2) > FAIL: MIPS II load $zero (mips64r3) > FAIL: MIPS II load $zero (mips64r5) > FAIL: MIPS II load $zero (mips64r6) > FAIL: MIPS II load $zero (octeon) > FAIL: MIPS II load $zero (octeon2) > FAIL: MIPS II load $zero (octeon3) > FAIL: MIPS II load $zero (octeonp) > FAIL: MIPS II load $zero (r4000) > FAIL: MIPS II load $zero (sb1) > FAIL: MIPS II load $zero (vr5400) > FAIL: MIPS II load $zero (xlr) > FAIL: MIPS III load $zero (mips3) > FAIL: MIPS III load $zero (mips4) > FAIL: MIPS III load $zero (mips5) > FAIL: MIPS III load $zero (mips64) > FAIL: MIPS III load $zero (mips64r2) > FAIL: MIPS III load $zero (mips64r3) > FAIL: MIPS III load $zero (mips64r5) > FAIL: MIPS III load $zero (mips64r6) > FAIL: MIPS III load $zero (octeon) > FAIL: MIPS III load $zero (octeon2) > FAIL: MIPS III load $zero (octeon3) > FAIL: MIPS III load $zero (octeonp) > FAIL: MIPS III load $zero (r4000) > FAIL: MIPS III load $zero (sb1) > FAIL: MIPS III load $zero (vr5400) > FAIL: MIPS III load $zero (xlr) > FAIL: MIPS ELF reloc 28 (LLD/SCD, n32) > FAIL: MIPS ELF reloc 28 (LLD/SCD, n64) > FAIL: Full MIPS R5900 > FAIL: MIPS MIPSR6 instructions (mips32r6) > FAIL: MIPS MIPSR6 instructions (mips64r6) > FAIL: MIPS MIPSR6 instructions (mips64r6) > FAIL: MIPS MIPSR6 instructions (mips64r6) > FAIL: MIPS64r6 n32 instructions (mips64r6) > FAIL: MIPS64r6 n64 instructions (mips64r6) > > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/indirect.exp ... > FAIL: Run indirect5 1 > FAIL: Run indirect5 2 > FAIL: Run indirect6 1 > FAIL: Run indirect6 2 > FAIL: indirect5a dynsym > FAIL: indirect5b dynsym > FAIL: indirect6a dynsym > FAIL: indirect6b dynsym > FAIL: Run indirect5 3 > FAIL: Run indirect5 4 > FAIL: Run indirect6 3 > FAIL: Run indirect6 4 > FAIL: indirect5c dynsym > FAIL: indirect5d dynsym > FAIL: indirect6c dynsym > FAIL: indirect6d dynsym > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/shared.exp ... > FAIL: Build libpr16496b.so > FAIL: Run pr2404 > FAIL: Run pr2404n > FAIL: Run pr2404 with PIE > FAIL: Run pr2404 with PIE (-z now) > FAIL: Run pr21964-4 > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elfvers/vers.exp ... > FAIL: vers24a > FAIL: vers24b > FAIL: vers24c > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-gc/gc.exp ... > FAIL: --gc-sections with --defsym > FAIL: --gc-sections with KEEP > FAIL: --gc-sections with __start_SECTIONNAME > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-plugin/lto.exp ... > FAIL: PR ld/12982 > FAIL: ld-plugin/lto-3r > FAIL: ld-plugin/lto-5r > FAIL: PR ld/19317 (2) > FAIL: PR ld/15323 (4) > FAIL: PR ld/19317 (3) > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-plugin/plugin.exp ... > FAIL: plugin claimfile lost symbol > FAIL: plugin claimfile replace symbol > FAIL: plugin claimfile resolve symbol > FAIL: plugin claimfile lost symbol with source > FAIL: plugin claimfile replace symbol with source > FAIL: plugin claimfile resolve symbol with source > FAIL: plugin 2 with source lib > FAIL: load plugin 2 with source > FAIL: plugin 3 with source lib > FAIL: load plugin 3 with source > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-shared/shared.exp ... > FAIL: shared (non PIC) > FAIL: shared (PIC main, non PIC so) > > > s390x-linux-gnu: > > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/shared.exp ... > FAIL: pr26580-3 > FAIL: Run pr21964-4 > > > ia64-linux-gnu: > > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ctf/ctf.exp ... > FAIL: Arrays (conflicted) > FAIL: Conflicted data syms, partially indexed, stripped, with variables > FAIL: Conflicted data syms, partially indexed, stripped > FAIL: Nonrepresentable types > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/elf.exp ... > FAIL: PR ld/22269 > FAIL: PR ld/22269 (-z dynamic-undefined-weak) > FAIL: Build pr26391-5.o > FAIL: Build pr26391-6.o > FAIL: Run pr26391-5 > FAIL: Run pr26391-6 > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/indirect.exp ... > FAIL: Run with libpr18720c.so 1 > FAIL: Run with libpr18720c.so 2 > FAIL: Run with libpr18720c.so 3 > FAIL: Run with libpr18720c.so 4 > FAIL: Run with libpr18720c.so 5 > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/shared.exp ... > FAIL: DT_TEXTREL map file warning > FAIL: pr22269-1 (static pie undefined weak) > FAIL: Run pr18718 > FAIL: Run pr18718 (-z now) > FAIL: Run pr18718 with PIE (1) > FAIL: Run pr18718 with PIE (2) > FAIL: Run pr18718 with PIE (3) > FAIL: Run pr18718 with PIE (4) > FAIL: Run pr18718 with PIC (1) > FAIL: Run pr18718 with PIC (2) > FAIL: Run pr18718 with PIC (3) > FAIL: Run pr18718 with PIC (4) > FAIL: Build pr23162a > FAIL: Build pr23162b > FAIL: Build libpr23161a.so > FAIL: Build pr23161a > FAIL: Build libpr23161b.so > FAIL: Build pr23161b > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/tls.exp ... > FAIL: Build pr22263-1 > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ifunc/ifunc.exp ... > FAIL: ifunc-using shared library does not contain R_*_IRELATIVE relocation > FAIL: Local ifunc-using executable does not contain R_*_IRELATIVE > relocation > FAIL: Static ifunc-using executable does not contain R_*_IRELATIVE > relocation > > > powerpc-linux-gnu: > > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ctf/ctf.exp ... > FAIL: Diagnostics - No parent dictionary > > > riscv64-linux-gnu: > > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/shared.exp ... > FAIL: Run pr21964-4 > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/tls.exp ... > FAIL: Build pr22263-1 > > > sparc64-linux-gnu: > > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/elf.exp ... > FAIL: Run pr26391-5 > FAIL: Run pr26391-6 > > > x86_64-linux-gnux32: > > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ctf/ctf.exp ... > FAIL: Diagnostics - No parent dictionary > > ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: The 2.40 branch has been created 2023-01-02 15:59 ` Christophe Lyon @ 2023-01-02 23:05 ` Mark Wielaard 2023-01-03 17:29 ` Christophe Lyon 2023-01-09 16:00 ` Christophe Lyon 1 sibling, 1 reply; 15+ messages in thread From: Mark Wielaard @ 2023-01-02 23:05 UTC (permalink / raw) To: Christophe Lyon; +Cc: Matthias Klose, Nick Clifton, binutils Hi Christophe, On Mon, Jan 02, 2023 at 04:59:40PM +0100, Christophe Lyon via Binutils wrote: > Thanks for catching this, I've just realized that Sourceware's > buildbot only runs a subset of binutils tests, which explains why > this wasn't noticed before. Ah, yeah, sorry. That is because the armhf builder still has debian old-stable installed, which had multiple ld tests failing (and it is pretty slow), so it only runs the binutils and gas testsuites, not the ld one. We could use your armhf_ubuntu20_04_worker or ubuntu20_04_armhf_worker to also run the binutils builds/tests. Cheers, Mark ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: The 2.40 branch has been created 2023-01-02 23:05 ` Mark Wielaard @ 2023-01-03 17:29 ` Christophe Lyon 2023-01-04 0:35 ` Mark Wielaard 0 siblings, 1 reply; 15+ messages in thread From: Christophe Lyon @ 2023-01-03 17:29 UTC (permalink / raw) To: Mark Wielaard; +Cc: Matthias Klose, Nick Clifton, binutils On 1/3/23 00:05, Mark Wielaard wrote: > Hi Christophe, > > On Mon, Jan 02, 2023 at 04:59:40PM +0100, Christophe Lyon via Binutils wrote: >> Thanks for catching this, I've just realized that Sourceware's >> buildbot only runs a subset of binutils tests, which explains why >> this wasn't noticed before. > > Ah, yeah, sorry. That is because the armhf builder still has debian > old-stable installed, which had multiple ld tests failing (and it is > pretty slow), so it only runs the binutils and gas testsuites, not the > ld one. > > We could use your armhf_ubuntu20_04_worker or ubuntu20_04_armhf_worker > to also run the binutils builds/tests. > Actually we have: armhf-ubuntu20_04 and armhf-ubuntu22_04 to build GDB and ubuntu22_04-armhf to build GCC The containers we use to build GDB have less cores than the ones we use for GCC. If we add binutils builders on the same workers as GDB, will they cooperate nicely (as in "do not compete for CPU", ie. be scheduled at different times)? If yes, maybe it makes sense to add binutils builders to: armhf-ubuntu20_04 armhf-ubuntu22_04 arm64-ubuntu20_04 arm64-ubuntu22_04 WDYT? Thanks, Christophe > Cheers, > > Mark ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: The 2.40 branch has been created 2023-01-03 17:29 ` Christophe Lyon @ 2023-01-04 0:35 ` Mark Wielaard 2023-01-04 10:31 ` Christophe Lyon 0 siblings, 1 reply; 15+ messages in thread From: Mark Wielaard @ 2023-01-04 0:35 UTC (permalink / raw) To: Christophe Lyon; +Cc: Matthias Klose, Nick Clifton, binutils, buildbot [-- Attachment #1: Type: text/plain, Size: 856 bytes --] Hi Christophe, On Tue, Jan 03, 2023 at 06:29:30PM +0100, Christophe Lyon wrote: > Actually we have: > armhf-ubuntu20_04 and armhf-ubuntu22_04 to build GDB and > ubuntu22_04-armhf to build GCC > > The containers we use to build GDB have less cores than the ones we > use for GCC. If we add binutils builders on the same workers as GDB, > will they cooperate nicely (as in "do not compete for CPU", ie. be > scheduled at different times)? > > If yes, maybe it makes sense to add binutils builders to: > armhf-ubuntu20_04 > armhf-ubuntu22_04 > arm64-ubuntu20_04 > arm64-ubuntu22_04 > > WDYT? That makes sense. Yes, they will cooperate nicely because the workers all have max_builds=1. So if there are multiple builds that could use the same worker they will just wait in the pending queue. I'll push the following to try the new builders. Thanks, Mark [-- Attachment #2: 0001-Add-binutils-ubuntu20_04-and-ubuntu22_04-armhf-and-a.patch --] [-- Type: text/plain, Size: 2566 bytes --] From e125fa6b21d87c8bb39649299762cdfbafe0282e Mon Sep 17 00:00:00 2001 From: Mark Wielaard <mark@klomp.org> Date: Wed, 4 Jan 2023 01:16:18 +0100 Subject: [PATCH] Add binutils ubuntu20_04 and ubuntu22_04 armhf and arm64 builders --- builder/master.cfg | 34 +++++++++++++++++++++++++++++++++- 1 file changed, 33 insertions(+), 1 deletion(-) diff --git a/builder/master.cfg b/builder/master.cfg index 8a66ae8..b16bb29 100644 --- a/builder/master.cfg +++ b/builder/master.cfg @@ -702,7 +702,11 @@ binutils_scheduler = schedulers.SingleBranchScheduler( "binutils-debian-i386", "binutils-fedora-ppc64le", "binutils-opensusetw-x86_64", - "binutils-opensuseleap-x86_64"]) + "binutils-opensuseleap-x86_64", + "binutils-ubuntu20_04-armhf", + "binutils-ubuntu22_04-armhf", + "binutils-ubuntu20_04-arm64", + "binutils-ubuntu22_04-arm64"]) c['schedulers'].append(binutils_scheduler) binutils_try_scheduler = schedulers.AnyBranchScheduler( @@ -2331,6 +2335,34 @@ binutils_opensuseleap_x86_64_builder = util.BuilderConfig( factory=binutils_factory) c['builders'].append(binutils_opensuseleap_x86_64_builder) +binutils_ubuntu20_04_armhf_builder = util.BuilderConfig( + name="binutils-ubuntu20_04-armhf", + workernames=["armhf-ubuntu20_04"], + tags=["binutils", "armhf", "ubuntu"], + factory=binutils_factory) +c['builders'].append(binutils_ubuntu20_04_armhf_builder) + +binutils_ubuntu22_04_armhf_builder = util.BuilderConfig( + name="binutils-ubuntu22_04-armhf", + workernames=["armhf-ubuntu22_04"], + tags=["binutils", "armhf", "ubuntu"], + factory=binutils_factory) +c['builders'].append(binutils_ubuntu22_04_armhf_builder) + +binutils_ubuntu20_04_arm64_builder = util.BuilderConfig( + name="binutils-ubuntu20_04-arm64", + workernames=["arm64-ubuntu20_04"], + tags=["binutils", "arm64", "ubuntu"], + factory=binutils_factory) +c['builders'].append(binutils_ubuntu20_04_arm64_builder) + +binutils_ubuntu22_04_arm64_builder = util.BuilderConfig( + name="binutils-ubuntu22_04-arm64", + workernames=["arm64-ubuntu22_04"], + tags=["binutils", "arm64", "ubuntu"], + factory=binutils_factory) +c['builders'].append(binutils_ubuntu22_04_arm64_builder) + binutils_rawhide_x86_64_builder = util.BuilderConfig( name="binutils-rawhide-x86_64", properties={'container-file': -- 2.31.1 ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: The 2.40 branch has been created 2023-01-04 0:35 ` Mark Wielaard @ 2023-01-04 10:31 ` Christophe Lyon 2023-01-04 11:07 ` Mark Wielaard 0 siblings, 1 reply; 15+ messages in thread From: Christophe Lyon @ 2023-01-04 10:31 UTC (permalink / raw) To: Mark Wielaard; +Cc: Matthias Klose, Nick Clifton, binutils, buildbot On 1/4/23 01:35, Mark Wielaard wrote: > Hi Christophe, > > On Tue, Jan 03, 2023 at 06:29:30PM +0100, Christophe Lyon wrote: >> Actually we have: >> armhf-ubuntu20_04 and armhf-ubuntu22_04 to build GDB and >> ubuntu22_04-armhf to build GCC >> >> The containers we use to build GDB have less cores than the ones we >> use for GCC. If we add binutils builders on the same workers as GDB, >> will they cooperate nicely (as in "do not compete for CPU", ie. be >> scheduled at different times)? >> >> If yes, maybe it makes sense to add binutils builders to: >> armhf-ubuntu20_04 >> armhf-ubuntu22_04 >> arm64-ubuntu20_04 >> arm64-ubuntu22_04 >> >> WDYT? > > That makes sense. Yes, they will cooperate nicely because the workers > all have max_builds=1. So if there are multiple builds that could use > the same worker they will just wait in the pending queue. > > I'll push the following to try the new builders. Thanks! I see they are all failing currently ;-) I have sent patches for the armhf failures yesterday, so they will hopefully become green soon. I don't understand why the arm64 ones are failing, is it because there is one linker test with XPASS? (I didn't notice any "unexpected failure" in the .sum summaries) Christophe > > Thanks, > > Mark ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: The 2.40 branch has been created 2023-01-04 10:31 ` Christophe Lyon @ 2023-01-04 11:07 ` Mark Wielaard 0 siblings, 0 replies; 15+ messages in thread From: Mark Wielaard @ 2023-01-04 11:07 UTC (permalink / raw) To: Christophe Lyon; +Cc: Matthias Klose, Nick Clifton, binutils, buildbot Hi Christophe, On Wed, Jan 04, 2023 at 11:31:50AM +0100, Christophe Lyon wrote: > >I'll push the following to try the new builders. > > Thanks! > > I see they are all failing currently ;-) > I have sent patches for the armhf failures yesterday, so they will > hopefully become green soon. > I don't understand why the arm64 ones are failing, is it because > there is one linker test with XPASS? (I didn't notice any > "unexpected failure" in the .sum summaries) Yes, the "XPASS: Run pr19719 fun undefined" is unexpected and so fails make check. Note that same XPASS on binutils-fedora-arm64, but that also has an extra FAIL: Build pr26094-1 Cheers, Mark ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: The 2.40 branch has been created 2023-01-02 15:59 ` Christophe Lyon 2023-01-02 23:05 ` Mark Wielaard @ 2023-01-09 16:00 ` Christophe Lyon 1 sibling, 0 replies; 15+ messages in thread From: Christophe Lyon @ 2023-01-09 16:00 UTC (permalink / raw) To: Matthias Klose, Nick Clifton, binutils Hi Matthias, On 1/2/23 16:59, Christophe Lyon via Binutils wrote: > Hi Matthias! > > On 1/2/23 12:41, Matthias Klose via Binutils wrote: >> On 31.12.22 14:00, Nick Clifton via Binutils wrote: >>> Hi Everyone, >>> >>> The 2.40 branch has now been created: >>> >>> git clone git://sourceware.org/git/binutils-gdb.git -b >>> binutils-2_40-branch >>> >>> A snapshot of the sources is also available here: >>> >>> https://sourceware.org/pub/binutils/snapshots/binutils-2.39.90.tar.xz >>> >>> Please could all patches for the branch be run by me. >>> The rules for the branch are: >>> >>> * No new features. >>> * Target specific bug fixes are OK. >>> * Generic bug fixes are OK if they are important and widely tested. >>> * Documentation updates/fixes are OK. >>> * Translation updates are OK. >>> * Fixes for testsuite failures are OK. >>> >>> Ideally I would like to make the release happen in two weeks time, >>> i.e. Jan 14, 2023. Which I hope will be enough time for everyone >>> to get their final fixes in. >> >> No test failures on amd64, ppc64el, ppc64. >> >> No test results yet for alpha, m68k, sh4, the hurd and KFreeBSD. >> >> For riscv64, there also is PR29940. >> >> Looks like libbacktrace is not built at build time, but only at test >> time when running make check. >> >> >> aarch64-linux-gnu: >> >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-aarch64/aarch64-elf.exp ... >> FAIL: ld-aarch64/tls-relax-gdesc-le-now >> >> >> arm-linux-gnueabi: >> >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/tls.exp ... >> FAIL: Build pr22263-1 >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ifunc/ifunc.exp ... >> FAIL: Run pr18841 with libpr18841b.so >> FAIL: Run pr18841 with libpr18841c.so >> FAIL: Run pr18841 with libpr18841bn.so (-z now) >> FAIL: Run pr18841 with libpr18841cn.so (-z now) >> FAIL: Run pr23169a >> FAIL: Run pr23169d >> >> >> arm-linux-gnueabihf: >> >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ifunc/ifunc.exp ... >> FAIL: Run pr18841 with libpr18841b.so >> FAIL: Run pr18841 with libpr18841c.so >> FAIL: Run pr18841 with libpr18841bn.so (-z now) >> FAIL: Run pr18841 with libpr18841cn.so (-z now) > > I have reproduced these errors and I have a simple fix I hope to post > shortly. > > Thanks for catching this, I've just realized that Sourceware's buildbot > only runs a subset of binutils tests, which explains why this wasn't > noticed before. I've now pushed fixes for pr18831 and pr23169. Thanks, Christophe > > Christophe > >> FAIL: Run pr23169a >> FAIL: Run pr23169d >> >> i686-linux-gnu: >> >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ctf/ctf.exp ... >> FAIL: Diagnostics - No parent dictionary >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-i386/i386.exp ... >> FAIL: Run pr19031 >> FAIL: Run got1 >> FAIL: Undefined weak symbol (-fPIE -no-pie) >> FAIL: Undefined weak symbol (-fPIE -pie) >> >> >> mipsel-linux-gnu (gas and ld): >> >> Running /<<PKGBUILDDIR>>/gas/testsuite/gas/mips/mips.exp ... >> FAIL: MIPS RM7000 workarounds test 2 (mips3) >> FAIL: MIPS RM7000 workarounds test 2 (mips4) >> FAIL: MIPS RM7000 workarounds test 2 (mips5) >> FAIL: MIPS RM7000 workarounds test 2 (mips64) >> FAIL: MIPS RM7000 workarounds test 2 (mips64r2) >> FAIL: MIPS RM7000 workarounds test 2 (mips64r3) >> FAIL: MIPS RM7000 workarounds test 2 (mips64r5) >> FAIL: MIPS RM7000 workarounds test 2 (octeon) >> FAIL: MIPS RM7000 workarounds test 2 (octeon2) >> FAIL: MIPS RM7000 workarounds test 2 (octeon3) >> FAIL: MIPS RM7000 workarounds test 2 (octeonp) >> FAIL: MIPS RM7000 workarounds test 2 (r4000) >> FAIL: MIPS RM7000 workarounds test 2 (sb1) >> FAIL: MIPS RM7000 workarounds test 2 (vr5400) >> FAIL: MIPS RM7000 workarounds test 2 (xlr) >> FAIL: MIPS II load $zero (interaptiv-mr2) >> FAIL: MIPS II load $zero (mips2) >> FAIL: MIPS II load $zero (mips3) >> FAIL: MIPS II load $zero (mips4) >> FAIL: MIPS II load $zero (mips5) >> FAIL: MIPS II load $zero (mips32) >> FAIL: MIPS II load $zero (mips32r2) >> FAIL: MIPS II load $zero (mips32r3) >> FAIL: MIPS II load $zero (mips32r5) >> FAIL: MIPS II load $zero (mips32r6) >> FAIL: MIPS II load $zero (mips64) >> FAIL: MIPS II load $zero (mips64r2) >> FAIL: MIPS II load $zero (mips64r3) >> FAIL: MIPS II load $zero (mips64r5) >> FAIL: MIPS II load $zero (mips64r6) >> FAIL: MIPS II load $zero (octeon) >> FAIL: MIPS II load $zero (octeon2) >> FAIL: MIPS II load $zero (octeon3) >> FAIL: MIPS II load $zero (octeonp) >> FAIL: MIPS II load $zero (r4000) >> FAIL: MIPS II load $zero (sb1) >> FAIL: MIPS II load $zero (vr5400) >> FAIL: MIPS II load $zero (xlr) >> FAIL: MIPS III load $zero (mips3) >> FAIL: MIPS III load $zero (mips4) >> FAIL: MIPS III load $zero (mips5) >> FAIL: MIPS III load $zero (mips64) >> FAIL: MIPS III load $zero (mips64r2) >> FAIL: MIPS III load $zero (mips64r3) >> FAIL: MIPS III load $zero (mips64r5) >> FAIL: MIPS III load $zero (mips64r6) >> FAIL: MIPS III load $zero (octeon) >> FAIL: MIPS III load $zero (octeon2) >> FAIL: MIPS III load $zero (octeon3) >> FAIL: MIPS III load $zero (octeonp) >> FAIL: MIPS III load $zero (r4000) >> FAIL: MIPS III load $zero (sb1) >> FAIL: MIPS III load $zero (vr5400) >> FAIL: MIPS III load $zero (xlr) >> FAIL: MIPS ELF reloc 28 (LLD/SCD, n32) >> FAIL: MIPS ELF reloc 28 (LLD/SCD, n64) >> FAIL: Full MIPS R5900 >> FAIL: MIPS MIPSR6 instructions (mips32r6) >> FAIL: MIPS MIPSR6 instructions (mips64r6) >> FAIL: MIPS MIPSR6 instructions (mips64r6) >> FAIL: MIPS MIPSR6 instructions (mips64r6) >> FAIL: MIPS64r6 n32 instructions (mips64r6) >> FAIL: MIPS64r6 n64 instructions (mips64r6) >> >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/indirect.exp ... >> FAIL: Run indirect5 1 >> FAIL: Run indirect5 2 >> FAIL: Run indirect6 1 >> FAIL: Run indirect6 2 >> FAIL: indirect5a dynsym >> FAIL: indirect5b dynsym >> FAIL: indirect6a dynsym >> FAIL: indirect6b dynsym >> FAIL: Run indirect5 3 >> FAIL: Run indirect5 4 >> FAIL: Run indirect6 3 >> FAIL: Run indirect6 4 >> FAIL: indirect5c dynsym >> FAIL: indirect5d dynsym >> FAIL: indirect6c dynsym >> FAIL: indirect6d dynsym >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/shared.exp ... >> FAIL: Build libpr16496b.so >> FAIL: Run pr2404 >> FAIL: Run pr2404n >> FAIL: Run pr2404 with PIE >> FAIL: Run pr2404 with PIE (-z now) >> FAIL: Run pr21964-4 >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elfvers/vers.exp ... >> FAIL: vers24a >> FAIL: vers24b >> FAIL: vers24c >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-gc/gc.exp ... >> FAIL: --gc-sections with --defsym >> FAIL: --gc-sections with KEEP >> FAIL: --gc-sections with __start_SECTIONNAME >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-plugin/lto.exp ... >> FAIL: PR ld/12982 >> FAIL: ld-plugin/lto-3r >> FAIL: ld-plugin/lto-5r >> FAIL: PR ld/19317 (2) >> FAIL: PR ld/15323 (4) >> FAIL: PR ld/19317 (3) >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-plugin/plugin.exp ... >> FAIL: plugin claimfile lost symbol >> FAIL: plugin claimfile replace symbol >> FAIL: plugin claimfile resolve symbol >> FAIL: plugin claimfile lost symbol with source >> FAIL: plugin claimfile replace symbol with source >> FAIL: plugin claimfile resolve symbol with source >> FAIL: plugin 2 with source lib >> FAIL: load plugin 2 with source >> FAIL: plugin 3 with source lib >> FAIL: load plugin 3 with source >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-shared/shared.exp ... >> FAIL: shared (non PIC) >> FAIL: shared (PIC main, non PIC so) >> >> >> s390x-linux-gnu: >> >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/shared.exp ... >> FAIL: pr26580-3 >> FAIL: Run pr21964-4 >> >> >> ia64-linux-gnu: >> >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ctf/ctf.exp ... >> FAIL: Arrays (conflicted) >> FAIL: Conflicted data syms, partially indexed, stripped, with variables >> FAIL: Conflicted data syms, partially indexed, stripped >> FAIL: Nonrepresentable types >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/elf.exp ... >> FAIL: PR ld/22269 >> FAIL: PR ld/22269 (-z dynamic-undefined-weak) >> FAIL: Build pr26391-5.o >> FAIL: Build pr26391-6.o >> FAIL: Run pr26391-5 >> FAIL: Run pr26391-6 >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/indirect.exp ... >> FAIL: Run with libpr18720c.so 1 >> FAIL: Run with libpr18720c.so 2 >> FAIL: Run with libpr18720c.so 3 >> FAIL: Run with libpr18720c.so 4 >> FAIL: Run with libpr18720c.so 5 >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/shared.exp ... >> FAIL: DT_TEXTREL map file warning >> FAIL: pr22269-1 (static pie undefined weak) >> FAIL: Run pr18718 >> FAIL: Run pr18718 (-z now) >> FAIL: Run pr18718 with PIE (1) >> FAIL: Run pr18718 with PIE (2) >> FAIL: Run pr18718 with PIE (3) >> FAIL: Run pr18718 with PIE (4) >> FAIL: Run pr18718 with PIC (1) >> FAIL: Run pr18718 with PIC (2) >> FAIL: Run pr18718 with PIC (3) >> FAIL: Run pr18718 with PIC (4) >> FAIL: Build pr23162a >> FAIL: Build pr23162b >> FAIL: Build libpr23161a.so >> FAIL: Build pr23161a >> FAIL: Build libpr23161b.so >> FAIL: Build pr23161b >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/tls.exp ... >> FAIL: Build pr22263-1 >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ifunc/ifunc.exp ... >> FAIL: ifunc-using shared library does not contain R_*_IRELATIVE >> relocation >> FAIL: Local ifunc-using executable does not contain R_*_IRELATIVE >> relocation >> FAIL: Static ifunc-using executable does not contain R_*_IRELATIVE >> relocation >> >> >> powerpc-linux-gnu: >> >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ctf/ctf.exp ... >> FAIL: Diagnostics - No parent dictionary >> >> >> riscv64-linux-gnu: >> >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/shared.exp ... >> FAIL: Run pr21964-4 >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/tls.exp ... >> FAIL: Build pr22263-1 >> >> >> sparc64-linux-gnu: >> >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/elf.exp ... >> FAIL: Run pr26391-5 >> FAIL: Run pr26391-6 >> >> >> x86_64-linux-gnux32: >> >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ctf/ctf.exp ... >> FAIL: Diagnostics - No parent dictionary >> >> ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: The 2.40 branch has been created 2023-01-02 11:41 ` Matthias Klose ` (2 preceding siblings ...) 2023-01-02 15:59 ` Christophe Lyon @ 2023-01-04 12:16 ` Nick Alcock 2023-01-10 12:43 ` Nick Alcock 3 siblings, 1 reply; 15+ messages in thread From: Nick Alcock @ 2023-01-04 12:16 UTC (permalink / raw) To: binutils; +Cc: Nick Clifton, Matthias Klose On 2 Jan 2023, Matthias Klose via Binutils stated: > On 31.12.22 14:00, Nick Clifton via Binutils wrote: > i686-linux-gnu: > > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ctf/ctf.exp ... > FAIL: Diagnostics - No parent dictionary This seems to be a cross-platform issue, which is strange because I've never seen this test (ld/testsuite/ld-ctf/diag-parname.d) fail: for me, it doesn't fail now, even with current 2.40 branch. This stuff is not compiler-dependent, so I'd expect to see identical failures for everybody. If you assemble diag-parname.s (in the above directory) and link it with the built linker with ld --shared --ctf-variables, what does it say? You *should* get something like CTF error: /usr/src/binutils-gdb/ld/testsuite/ld-ctf/A.c (0): lookup failure for type 3: flags 1 CTF error: /usr/src/binutils-gdb/ld/testsuite/ld-ctf/A.c (0): error doing struct/union member type hashing: during type hashing for type 80000001, kind 6 CTF error: deduplication failed for /usr/src/binutils-gdb/ld/testsuite/ld-ctf/A.c ./ld-new: warning: CTF linking failed; output will have no CTF section: The parent CTF dictionary is unavailable. As usual, only the warning on the last line matters. Not a blocker in any case: this only affects corrupted input, and the linker has bigger problems with corrupted CTF input right now (it is trivially easy to make it infloop for starters: I have a fix planned). > ia64-linux-gnu: > > Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ctf/ctf.exp ... > FAIL: Arrays (conflicted) > FAIL: Conflicted data syms, partially indexed, stripped, with variables > FAIL: Conflicted data syms, partially indexed, stripped > FAIL: Nonrepresentable types I'd like to fix these, but there is no ia64 machine in the compile farm that I can see, and these days they're as rare as hen's teeth. I suspect something's up with the compiler's CTF generation (in the first and last case) or with its handling of hidden symbols (in the middle two: just handling them like GCC 11 did would be enough to make those two tests fail). ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: The 2.40 branch has been created 2023-01-04 12:16 ` Nick Alcock @ 2023-01-10 12:43 ` Nick Alcock 0 siblings, 0 replies; 15+ messages in thread From: Nick Alcock @ 2023-01-10 12:43 UTC (permalink / raw) To: binutils; +Cc: Nick Alcock, Nick Clifton, Matthias Klose On 4 Jan 2023, Nick Alcock via Binutils stated: > On 2 Jan 2023, Matthias Klose via Binutils stated: >> On 31.12.22 14:00, Nick Clifton via Binutils wrote: >> i686-linux-gnu: >> >> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ctf/ctf.exp ... >> FAIL: Diagnostics - No parent dictionary > > This seems to be a cross-platform issue, which is strange because I've > never seen this test (ld/testsuite/ld-ctf/diag-parname.d) fail: for me, > it doesn't fail now, even with current 2.40 branch. This stuff is not > compiler-dependent, so I'd expect to see identical failures for > everybody. I have a fix for this one under test (see the last patch in the series I just sent). It's a type confusion that involves treating one struct as if it were a much bigger one (and then writing to it, ugh), so it comes down to accessing uninitialized memory. Hence the irreproducibility. I'll backport the fix to all affected branches (2.36+). This is now bug 29983. ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: The 2.40 branch has been created 2022-12-31 13:00 The 2.40 branch has been created Nick Clifton 2023-01-02 11:41 ` Matthias Klose @ 2023-01-04 3:05 ` Alan Modra 2023-01-04 9:36 ` Nick Clifton 1 sibling, 1 reply; 15+ messages in thread From: Alan Modra @ 2023-01-04 3:05 UTC (permalink / raw) To: Nick Clifton; +Cc: binutils Hi Nick, Would you like me to apply the copyright year update to the branch? Also, the libiberty update should have merged gcc's config/picflag.m4 with ours, in order for libiberty/configure to regen without differences on the branch. I'm going to apply the following mainline, and will backport to the branch if that's OK? diff --git a/config/picflag.m4 b/config/picflag.m4 index 3bd49af00e5..3f3ac744c96 100644 --- a/config/picflag.m4 +++ b/config/picflag.m4 @@ -44,6 +44,9 @@ case "${$2}" in # sets the default TLS model and affects inlining. $1=-fPIC ;; + loongarch*-*-*) + $1=-fpic + ;; mips-sgi-irix6*) # PIC is the default. ;; diff --git a/libiberty/configure b/libiberty/configure index 451af4978e7..1ccfac9fb11 100755 --- a/libiberty/configure +++ b/libiberty/configure @@ -5349,6 +5349,9 @@ case "${host}" in # sets the default TLS model and affects inlining. PICFLAG=-fPIC ;; + loongarch*-*-*) + PICFLAG=-fpic + ;; mips-sgi-irix6*) # PIC is the default. ;; -- Alan Modra Australia Development Lab, IBM ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: The 2.40 branch has been created 2023-01-04 3:05 ` Alan Modra @ 2023-01-04 9:36 ` Nick Clifton 0 siblings, 0 replies; 15+ messages in thread From: Nick Clifton @ 2023-01-04 9:36 UTC (permalink / raw) To: Alan Modra; +Cc: binutils Hi Alan, > Would you like me to apply the copyright year update to the branch? Yes please. (I should have thought of this and delayed branching until after the start of the new year. Doh). > Also, the libiberty update should have merged gcc's config/picflag.m4 > with ours, in order for libiberty/configure to regen without > differences on the branch. I'm going to apply the following mainline, > and will backport to the branch if that's OK? Totally OK, please do. Aside - keeping our version of libiberty in sync with gcc, but with local tweaks is becoming burdensome... Cheers Nick ^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2023-01-10 12:43 UTC | newest] Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2022-12-31 13:00 The 2.40 branch has been created Nick Clifton 2023-01-02 11:41 ` Matthias Klose 2023-01-02 11:56 ` Matthias Klose 2023-01-02 12:03 ` Andreas Schwab 2023-01-02 15:59 ` Christophe Lyon 2023-01-02 23:05 ` Mark Wielaard 2023-01-03 17:29 ` Christophe Lyon 2023-01-04 0:35 ` Mark Wielaard 2023-01-04 10:31 ` Christophe Lyon 2023-01-04 11:07 ` Mark Wielaard 2023-01-09 16:00 ` Christophe Lyon 2023-01-04 12:16 ` Nick Alcock 2023-01-10 12:43 ` Nick Alcock 2023-01-04 3:05 ` Alan Modra 2023-01-04 9:36 ` Nick Clifton
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).