From: "H.J. Lu" <hjl.tools@gmail.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: Nick Clifton <nickc@redhat.com>, Binutils <binutils@sourceware.org>
Subject: Re: The 2.38 branch has been created.
Date: Sun, 30 Jan 2022 07:02:42 -0800 [thread overview]
Message-ID: <CAMe9rOpe1Xt3obmuk9QfyUUonKmcirRGsWNrGSrbOrtM_hueJg@mail.gmail.com> (raw)
In-Reply-To: <520819c4-bf77-8cba-1dc1-a21bffb62a64@ubuntu.com>
On Tue, Jan 25, 2022 at 4:39 AM Matthias Klose <doko@ubuntu.com> wrote:
>
> On 1/22/22 13:58, Nick Clifton via Binutils wrote:
> > Hi Everyone,
> >
> > The 2.38 branch has now been created:
> >
> > git clone git://sourceware.org/git/binutils-gdb.git -b binutils-2_38-branch
> >
> > A snapshot of the sources is also available here:
> >
> > https://sourceware.org/pub/binutils/snapshots/binutils-2.37.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. Saturday 5th Feb 2022. Which I hope will be enough time for
> > everyone to get their final fixes in.
>
> some issues:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=28819
> has a reproducer to show that a ld change between Jan 06 and Jan 19 builds
> binaries without RELRO support on at least some architectures.
>
> this is a build configured with -enable-pgo-build=lto.
>
> on any arch:
> make[5]: Entering directory '/<<PKGBUILDDIR>>/builddir-single/libbacktrace'
> FAIL: allocfail.sh
>
>
> libbacktrace seems not to be built during the build, but only when running the
> tests. Is this expected?
>
> test results for various architectures:
>
> amd64, ppc64, hppa, powerpc, x32: no test failures
>
>
> arm64, regression from 2.37:
> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-aarch64/aarch64-elf.exp ...
> FAIL: ld-aarch64/tls-relax-gdesc-le-now
>
> armel, armhf:
> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/elf.exp ...
> FAIL: .noinit sections
> FAIL: .persistent sections
> 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
>
>
> i686 (regressions):
> 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)
>
I can't reproduce this with --enable-pgo-build=lto using GCC 11.2.
Which GCC are you using? Does it fail without --enable-pgo-build=lto?
--
H.J.
next prev parent reply other threads:[~2022-01-30 15:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 12:58 Nick Clifton
2022-01-23 13:15 ` H.J. Lu
2022-01-23 13:32 ` [PATCH] Regenerate configure files with autoconf 2.69 H.J. Lu
2022-01-24 14:59 ` The 2.38 branch has been created Nick Clifton
2022-01-25 12:39 ` Matthias Klose
2022-01-25 15:37 ` Nick Clifton
2022-01-29 5:29 ` Alan Modra
2022-01-30 13:32 ` Matthias Klose
2022-01-30 13:53 ` H.J. Lu
2022-01-30 13:58 ` Matthias Klose
2022-01-30 22:48 ` Alan Modra
2022-01-25 17:22 ` Szabolcs Nagy
2022-01-27 10:18 ` Szabolcs Nagy
2022-01-30 15:02 ` H.J. Lu [this message]
2022-02-08 2:07 ` Palmer Dabbelt
2022-02-08 15:43 ` Nick Clifton
2022-02-09 9:21 ` Fangrui Song
[not found] ` <MWHPR1201MB0110C2AE8A32FAF1A45EFEE4CB2E9@MWHPR1201MB0110.namprd12.prod.outlook.com>
2022-02-09 15:50 ` Nick Clifton
2022-02-10 4:53 ` Fangrui Song
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=CAMe9rOpe1Xt3obmuk9QfyUUonKmcirRGsWNrGSrbOrtM_hueJg@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=doko@ubuntu.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).