From: Alan Modra <amodra@gmail.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: Nick Clifton <nickc@redhat.com>, binutils@sourceware.org
Subject: Re: The 2.38 branch has been created.
Date: Mon, 31 Jan 2022 09:18:38 +1030 [thread overview]
Message-ID: <YfcVxlo/Vco8suqH@squeak.grove.modra.org> (raw)
In-Reply-To: <5ceb36ab-5d78-ae60-809a-9a5ae73bfd01@ubuntu.com>
On Sun, Jan 30, 2022 at 02:32:11PM +0100, Matthias Klose wrote:
> On 1/29/22 06:29, Alan Modra wrote:
> > On Tue, Jan 25, 2022 at 03:37:08PM +0000, Nick Clifton via Binutils wrote:
> >>> 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...
> >
> > I would if I could reproduce it. My builds are OK. Matthias,
> > ld/ld.log might give me a clue, if that is available somewhere.
>
> Attached. This is triggered by configuring with --enable-pgo-build=lto. The
> tests pass when binutils is configured without that option.
My --enable-pgo-build=lto was fine, but your compiler was different to
mine. The log shows failures caused by gcc inform messages like:
../bfd/../../bfd/elfcode.h: In function 'bfd_elf64_swap_symbol_in':
../bfd/../../bfd/elfcode.h:189:16: note: the layout of aggregates containing vectors with 2-byte alignment has changed in GCC 5
189 | dst->st_info = H_GET_8 (abfd, src->st_info);
Don't ask me why you're getting that inform message. There are no
vector fields let alone 2-byte aligned vector fields in either
elf_internal_sym or Elf64_External_Sym.
Anyway, dejagnu fails a test on any unexpected output that isn't
trimmed by prune_warnings. So not actually a linker failure.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2022-01-30 22:48 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 [this message]
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=YfcVxlo/Vco8suqH@squeak.grove.modra.org \
--to=amodra@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).