* 2.41 branch created
@ 2023-07-03 11:13 Nick Clifton
2023-07-21 10:05 ` Maciej W. Rozycki
` (2 more replies)
0 siblings, 3 replies; 7+ messages in thread
From: Nick Clifton @ 2023-07-03 11:13 UTC (permalink / raw)
To: binutils
Hi Everyone,
The 2.41 branch has now been created:
git clone git://sourceware.org/git/binutils-gdb.git -b binutils-2_41-branch
A snapshot of the sources is also available here:
https://sourceware.org/pub/binutils/snapshots/binutils-2.40.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. 23 July. Which I hope will be enough time for everyone
to get their final fixes in.
Cheers
Nick
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 2.41 branch created
2023-07-03 11:13 2.41 branch created Nick Clifton
@ 2023-07-21 10:05 ` Maciej W. Rozycki
2023-07-21 15:47 ` Nick Clifton
2023-07-28 5:51 ` Jan Beulich
2023-07-30 0:55 ` Matthias Klose
2 siblings, 1 reply; 7+ messages in thread
From: Maciej W. Rozycki @ 2023-07-21 10:05 UTC (permalink / raw)
To: Nick Clifton; +Cc: binutils
On Mon, 3 Jul 2023, Nick Clifton via Binutils wrote:
> Ideally I would like to make the release happen in two weeks time,
> i.e. 23 July. Which I hope will be enough time for everyone
> to get their final fixes in.
Nick, please hold on with the release until the incompatible MIPS change
discussed here:
<https://sourceware.org/pipermail/binutils/2023-July/128495.html> has been
sorted.
Maciej
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 2.41 branch created
2023-07-21 10:05 ` Maciej W. Rozycki
@ 2023-07-21 15:47 ` Nick Clifton
2023-07-28 5:18 ` Maciej W. Rozycki
0 siblings, 1 reply; 7+ messages in thread
From: Nick Clifton @ 2023-07-21 15:47 UTC (permalink / raw)
To: Maciej W. Rozycki; +Cc: binutils
Hi Maciej,
>> Ideally I would like to make the release happen in two weeks time,
>> i.e. 23 July.
> Nick, please hold on with the release until the incompatible MIPS change
> discussed here:
> <https://sourceware.org/pipermail/binutils/2023-July/128495.html> has been
> sorted.
Certainly. Please can you let me know when you are ready.
Cheers
Nick
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 2.41 branch created
2023-07-21 15:47 ` Nick Clifton
@ 2023-07-28 5:18 ` Maciej W. Rozycki
0 siblings, 0 replies; 7+ messages in thread
From: Maciej W. Rozycki @ 2023-07-28 5:18 UTC (permalink / raw)
To: Nick Clifton; +Cc: binutils
Hi Nick,
> > Nick, please hold on with the release until the incompatible MIPS change
> > discussed here:
> > <https://sourceware.org/pipermail/binutils/2023-July/128495.html> has been
> > sorted.
>
> Certainly. Please can you let me know when you are ready.
I have pushed all the changes required for the MIPS port now.
There have been no actual code changes and the only non-testsuite changes
have been updates to MIPS sections of bfd/config.bfd, gas/configure.ac,
and ld/configure.tgt. Also I have regression-tested my patchset across my
usual set of MIPS and non-MIPS targets, so I am confident no harm has been
done with these changes.
Please go ahead with the release then and again apologies to you and
anyone this might have affected for the disruption caused.
Maciej
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 2.41 branch created
2023-07-03 11:13 2.41 branch created Nick Clifton
2023-07-21 10:05 ` Maciej W. Rozycki
@ 2023-07-28 5:51 ` Jan Beulich
2023-07-28 8:54 ` Nick Clifton
2023-07-30 0:55 ` Matthias Klose
2 siblings, 1 reply; 7+ messages in thread
From: Jan Beulich @ 2023-07-28 5:51 UTC (permalink / raw)
To: Nick Clifton; +Cc: binutils
Nick,
On 03.07.2023 13:13, Nick Clifton via Binutils wrote:
> Hi Everyone,
>
> The 2.41 branch has now been created:
>
> git clone git://sourceware.org/git/binutils-gdb.git -b binutils-2_41-branch
>
> A snapshot of the sources is also available here:
>
> https://sourceware.org/pub/binutils/snapshots/binutils-2.40.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. 23 July. Which I hope will be enough time for everyone
> to get their final fixes in.
with the MIPS things out of the way, I wonder if you would want to
further wait for the regression fix for PR gas/30688. The code
change as shown in the bug looks fine testing-wise, but I'm
struggling a little with the testsuite additions (targets once
again behave too differently in certain aspects). I expect to have
this sorted (and a final test run done) later in the day.
Jan
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 2.41 branch created
2023-07-28 5:51 ` Jan Beulich
@ 2023-07-28 8:54 ` Nick Clifton
0 siblings, 0 replies; 7+ messages in thread
From: Nick Clifton @ 2023-07-28 8:54 UTC (permalink / raw)
To: Jan Beulich; +Cc: binutils
Hi Jan,
> with the MIPS things out of the way, I wonder if you would want to
> further wait for the regression fix for PR gas/30688. The code
> change as shown in the bug looks fine testing-wise, but I'm
> struggling a little with the testsuite additions (targets once
> again behave too differently in certain aspects). I expect to have
> this sorted (and a final test run done) later in the day.
That should be fine. I am going to create the release this Sunday (30th)
so you have until for any last minute bug fixes.
Cheers
Nick
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 2.41 branch created
2023-07-03 11:13 2.41 branch created Nick Clifton
2023-07-21 10:05 ` Maciej W. Rozycki
2023-07-28 5:51 ` Jan Beulich
@ 2023-07-30 0:55 ` Matthias Klose
2 siblings, 0 replies; 7+ messages in thread
From: Matthias Klose @ 2023-07-30 0:55 UTC (permalink / raw)
To: binutils; +Cc: Vladimir Mezentsev
On 03.07.23 13:13, Nick Clifton via Binutils wrote:
> Hi Everyone,
>
> The 2.41 branch has now been created:
>
> git clone git://sourceware.org/git/binutils-gdb.git -b binutils-2_41-branch
>
> A snapshot of the sources is also available here:
>
> https://sourceware.org/pub/binutils/snapshots/binutils-2.40.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. 23 July. Which I hope will be enough time for everyone
> to get their final fixes in.
built the branch 47f6803e1df:
no failures on arm-linux-gnu*, power*-linux-gnu, hppa-linux-gnu, sparc64-linux-gnu
failures in the gprofng tests, there seems to be a stray file created:
$ cat <builddir>/gprofng/\&1
Error: Warning! Source file `tmpdir/setpath_map/src/t.c' is newer than the
experiment data
x86_64-linux-gnu:
Running /<<PKGBUILDDIR>>/gprofng/testsuite/gprofng.display/display.exp ...
ERROR: comparison of results in synprog failed
Running /<<PKGBUILDDIR>>/gprofng/testsuite/gprofng.display/gp-collect-app_F.exp ...
FAIL: tmpdir/gp-collect-app_F
i686-linux-gnu:
Running /<<PKGBUILDDIR>>/gprofng/testsuite/gprofng.display/display.exp ...
ERROR: comparison of results in synprog failed
Running /<<PKGBUILDDIR>>/gprofng/testsuite/gprofng.display/gp-collect-app_F.exp ...
FAIL: tmpdir/gp-collect-app_F
aarch64-linux-gnu:
Running /<<PKGBUILDDIR>>/gprofng/testsuite/gprofng.display/display.exp ...
ERROR: comparison of results in mttest failed
ERROR: comparison of results in synprog failed
Running /<<PKGBUILDDIR>>/gprofng/testsuite/gprofng.display/gp-collect-app_F.exp ...
FAIL: tmpdir/gp-collect-app_F
s390x-linux-gnu:
Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/shared.exp ...
FAIL: pr26580-3
FAIL: Run pr21964-4
mips64el-linux-gnu:
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 (allegrex)
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-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
FAIL: bootstrap with -Wl,-z,nosectionheader
Running /<<PKGBUILDDIR>>/ld/testsuite/ld-mips-elf/mips-elf.exp ...
FAIL: MIPS reloc estimation 1
mipsel-linux-gnu:
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 (allegrex)
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 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/no-section-header.exp ...
FAIL: Build pr25617-1a-now-no-sec-hdr.so (none)
FAIL: Build pr25617-1a-now-no-sec-hdr.so (objcopy)
FAIL: Build pr25617-1a-now-no-sec-hdr.so (strip)
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: vers4
FAIL: vers4b
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)
Running /<<PKGBUILDDIR>>/ld/testsuite/ld-shared/shared.exp ...
FAIL: shared (non PIC)
FAIL: shared (PIC main, non PIC so)
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)
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-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
m68k-linux-gnu:
Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/dwarf.exp ...
FAIL: Handle no DWARF information
Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/indirect.exp ...
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: DT_TEXTREL map file warning
FAIL: pr20995
FAIL: pr20995-2
FAIL: pr22269-1 (static pie undefined weak)
FAIL: Run pr2404 with PIE
FAIL: Run pr2404 with PIE (-z now)
FAIL: Run pr19719 fun undefined
Running /<<PKGBUILDDIR>>/ld/testsuite/ld-m68k/m68k.exp ...
FAIL: ld-m68k/tls-gd-2
FAIL: ld-m68k/tls-gd-ie-1
FAIL: ld-m68k/tls-ie-1
FAIL: ld-m68k/tls-ld-1
sh4-linux-gnu:
Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/dwarf.exp ...
FAIL: Handle no DWARF information
Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/shared.exp ...
FAIL: pr20995
FAIL: pr20995-2
FAIL: pr22269-1 (static pie undefined weak)
FAIL: Run pr19579
FAIL: Run pr19579 (-z now)
FAIL: Run pr19719 fun undefined
Running /<<PKGBUILDDIR>>/ld/testsuite/ld-plugin/lto.exp ...
FAIL: PR ld/12760
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2023-07-30 0:55 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-07-03 11:13 2.41 branch created Nick Clifton
2023-07-21 10:05 ` Maciej W. Rozycki
2023-07-21 15:47 ` Nick Clifton
2023-07-28 5:18 ` Maciej W. Rozycki
2023-07-28 5:51 ` Jan Beulich
2023-07-28 8:54 ` Nick Clifton
2023-07-30 0:55 ` Matthias Klose
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).