From: Nick Clifton <nickc@redhat.com>
To: Matthias Klose <doko@ubuntu.com>, binutils@sourceware.org
Subject: Re: The 2.38 branch has been created.
Date: Tue, 25 Jan 2022 15:37:08 +0000 [thread overview]
Message-ID: <b35cf789-a32e-5790-52f1-18b9a5436fda@redhat.com> (raw)
In-Reply-To: <520819c4-bf77-8cba-1dc1-a21bffb62a64@ubuntu.com>
Hi Matthias,
> 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.
Hmm, I had better check this out. Thanks for raising the issue.
> 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?
It was a snafu. (I accidentally deleted a file in the libbacktrace directory).
This should now be fixed.
> amd64, ppc64, hppa, powerpc, x32: no test failures
That is nice.
> arm64, regression from 2.37:
> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-aarch64/aarch64-elf.exp ...
> FAIL: ld-aarch64/tls-relax-gdesc-le-now
Hmm, I will check that one out.
> ppc64el:
> 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
I think that I will let Alan look into these...
> s390:
> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/shared.exp ...
> FAIL: pr26580-3
> FAIL: Run pr21964-4
> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/tls.exp ...
> FAIL: Build pr22263-1
I will have a look into these as well.
Cheers
Nick
next prev parent reply other threads:[~2022-01-25 15:37 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 [this message]
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
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=b35cf789-a32e-5790-52f1-18b9a5436fda@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=doko@ubuntu.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).