From: Alan Modra <amodra@gmail.com>
To: Mark Wielaard <mark@klomp.org>
Cc: binutils@sourceware.org, gdb@sourceware.org
Subject: Re: buildbot vs --enable-targets=all
Date: Tue, 26 Jul 2022 10:54:12 +0930 [thread overview]
Message-ID: <Yt9CPESJzTKwGhvG@squeak.grove.modra.org> (raw)
In-Reply-To: <94d446556e470859b878bb27eec5e2a52d063673.camel@klomp.org>
On Mon, Jul 25, 2022 at 02:25:42PM +0200, Mark Wielaard wrote:
> On debian-ppc64 and fedora-ppc64le there are the following ld failures:
> https://builder.sourceware.org/buildbot/#builders/86/builds/343
> https://builder.sourceware.org/buildbot/#builders/78/builds/382
>
> extra lines in dump.out starting with "^ 40: 0000002c 0
> TLS GLOBAL DEFAULT 9 ie0$"
> EOF from /var/lib/buildbot/workers/wildebeest/binutils-debian-
> ppc64/binutils-gdb/ld/testsuite/ld-powerpc/tlsexe32.r
> FAIL: TLS32 dynamic exec
The line should match the last line of ld-powerpc/tlsexe32.r. Three
possibilities occur to me that might cause this:
1) There really is a duplicate globel ie0 symbol, or readelf is
duplicating an output line.
2) expect/dejagnu is duplicating output lines to dump.out, or reading
that file back when matching regexps duplicates the last line.
3) The last line of tlsexe32.r is dropped from the git checkout, or
when matching regexps.
None of these things happen elsewhere as far as I know. ie. the build
bot is broken.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2022-07-26 1:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 12:25 Mark Wielaard
2022-07-26 1:24 ` Alan Modra [this message]
2022-07-26 11:46 ` Alan Modra
2022-07-26 12:43 ` Alan Modra
2022-07-26 12:55 ` Mark Wielaard
2022-07-26 1:59 ` Jeffrey Walton
2022-08-03 10:38 ` Mark Wielaard
2022-08-03 10:56 ` Andreas Schwab
2022-08-03 11:35 ` Luis Machado
2022-08-03 11:49 ` Mark Wielaard
2022-08-03 11:54 ` Luis Machado
2022-08-03 11:57 ` Mark Wielaard
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=Yt9CPESJzTKwGhvG@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=mark@klomp.org \
/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).