From: Nick Clifton <nickc@redhat.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: mark@klomp.org, binutils@sourceware.org
Subject: Re: ☠ Buildbot (Sourceware): binutils-gdb - failed test (failure) test (failure) (master)
Date: Tue, 16 Apr 2024 17:23:20 +0100 [thread overview]
Message-ID: <52b815f3-5127-47a6-b11b-efc2cc9fb3e6@redhat.com> (raw)
In-Reply-To: <mhng-31d6499c-9830-478c-9858-2ca9369ea43a@palmer-ri-x1c9a>
Hi Palmer,
> I can't think of any reason the RISC-V attributes would specifically trip up on an objcopy that doesn't change anything else. We've got some string-based attributes, but
> if nothing else changes they should stay the same too. There's also some attribute merging code, but again that shouldn't change anything.
>
> That said, I wouldn't be surprised if we have some bug floating around there somewhere. The attributes aren't all that widely used (they sort of just store a bunch of
> stuff that doesn't have much meaning, we've gotten burned by backwards compatability there a few times). I think tooling mostly ignores them these days.
>
> LMK if you want Nelson or I to look, but happpy to have the help ;)
Thanks for the offer, but I think that I have already found the problem.
The issue was that the .riscv_attributes section was appearing before
the .text section in BFD's list of sections to allocate to segments.
This was then tripping up on a bug in the fix for PR 31450 which made
the BFD library think that it needed to rework the section to segment
mapping which then meant that the RISCV_ATTRIBUTES segment was moved to
a different address which finally resulted in objcopy producing a changed
binary. (phew!)
Anyway I am testing a patch locally which I think will fix the problem.
Cheers
Nick
next prev parent reply other threads:[~2024-04-16 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 15:22 builder
2024-04-16 15:36 ` Mark Wielaard
2024-04-16 15:45 ` Nick Clifton
2024-04-16 15:54 ` Palmer Dabbelt
2024-04-16 16:23 ` Nick Clifton [this message]
2024-04-16 17:36 ` Palmer Dabbelt
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=52b815f3-5127-47a6-b11b-efc2cc9fb3e6@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=mark@klomp.org \
--cc=palmer@dabbelt.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).