public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Mark Wielaard <mark@klomp.org>
Cc: Binutils <binutils@sourceware.org>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: Re: New sourceware binutils-gentoo-sparc builders
Date: Sat, 14 Jan 2023 21:34:04 +0000	[thread overview]
Message-ID: <A4991FAD-0898-4CFC-B1C5-D69D8AA20993@gentoo.org> (raw)
In-Reply-To: <20230114210217.GA6963@gnu.wildebeest.org>

[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]



> On 14 Jan 2023, at 21:02, Mark Wielaard <mark@klomp.org> wrote:
> 
> Hi,
> 
> Thanks to Sam James, the Gentoo Foundation and OSUOSL
> builder.sourceware.org now has a gentoo-sparc worker [1]
> which runs binutils CI [2] and try [3] builders.
> 
> It seems in good shape with only two unexpected failures for
> the ld tests:

Thanks for the announcement!

> 
> [...]
>     === ld Summary ===
> 
> # of expected passes 1596
> # of unexpected failures 2
> # of expected failures 26
> # of untested testcases 1
> # of unsupported tests 157
> 
> The two ld FAILS are:
> 
> Running: tmpdir/pr26391-5 > tmpdir/pr26391-5.out
> child killed: illegal instruction
> FAIL: Run pr26391-5
> 
> Running: tmpdir/pr26391-6 > tmpdir/pr26391-6.out
> child killed: illegal instruction
> FAIL: Run pr26391-6

I've filed a bug for this at https://sourceware.org/bugzilla/show_bug.cgi?id=30002,
but in doing so, I ended up finding some interesting bits from the last few years.

glaubitz from Debian bisected the issue at https://sourceware.org/bugzilla/show_bug.cgi?id=26391#c10
and came up with:
```
496afd17055aeb7d8f45e01715c475664f2b73bd is the first bad commit
commit 496afd17055aeb7d8f45e01715c475664f2b73bd
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Sat Sep 12 05:37:30 2020 -0700

elf: Add -z unique-symbol to avoid duplicated local symbol names
```

but H.J Lu couldn't immediately find a reason why it would happen on
sparc, and then it looks like the issue was forgotten about.

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]

  reply	other threads:[~2023-01-14 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14 21:02 Mark Wielaard
2023-01-14 21:34 ` Sam James [this message]
2023-01-15  0:22   ` John Paul Adrian Glaubitz
2023-01-15  0:52     ` Sam James

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=A4991FAD-0898-4CFC-B1C5-D69D8AA20993@gentoo.org \
    --to=sam@gentoo.org \
    --cc=binutils@sourceware.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --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).