From: Christophe Lyon <christophe.lyon@arm.com>
To: Matthias Klose <matthias.klose@canonical.com>,
Nick Clifton <nickc@redhat.com>,
binutils@sourceware.org
Subject: Re: The 2.40 branch has been created
Date: Mon, 2 Jan 2023 16:59:40 +0100 [thread overview]
Message-ID: <e6fcc285-becc-5816-db4a-36e37e8c08cd@arm.com> (raw)
In-Reply-To: <35a47bed-36af-6f8a-55a6-9cef247f9840@canonical.com>
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
>
>
next prev parent reply other threads:[~2023-01-02 15:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 13:00 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 [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e6fcc285-becc-5816-db4a-36e37e8c08cd@arm.com \
--to=christophe.lyon@arm.com \
--cc=binutils@sourceware.org \
--cc=matthias.klose@canonical.com \
--cc=nickc@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).