From: Jan Beulich <jbeulich@suse.com>
To: Nelson Chu <nelson.chu@sifive.com>
Cc: Kito Cheng <kito.cheng@sifive.com>,
Binutils <binutils@sourceware.org>,
Jim Wilson <jim.wilson.gcc@gmail.com>,
Palmer Dabbelt <palmer@rivosinc.com>
Subject: Re: your patch "RISC-V: Add PT_RISCV_ATTRIBUTES and add it to PHDR"
Date: Fri, 11 Feb 2022 10:50:12 +0100 [thread overview]
Message-ID: <9848e976-ae7f-0644-18a7-f085ecd6228d@suse.com> (raw)
In-Reply-To: <CAJYME4GAZVH2ew-j0xgWYubZ0Y7epFrnPG6GkSdFQjrUgQsdbw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
On 11.02.2022 06:56, Nelson Chu wrote:
> On Thu, Feb 10, 2022 at 8:38 PM Jan Beulich via Binutils
> <binutils@sourceware.org> wrote:
>> it looks like it is this patch which has caused the ld-elf/seg-2
>> ld testcase to be failing in 2.38, as compared to 2.37. It's the
>> extra phdr which looks to be getting in the way. The testcase
>> already has a fair number of #xfail targets - perhaps RISC-V wants
>> adding there, too?
>
> After building the
> rv32i-newlib/rv64gc-newlib/rv32gc-glibc/rv64gc-glibc toolchains, with
> master branches of gcc and glibc, and the binutils 2.38 release
> branch, I don't see the error you mentioned. Could you give more
> information, like which gcc or glibc branch you are using? Or other
> details that might help.
Well, I'm observing this in a cross build on ix86. As per the test I
don't see how gcc could be involved (the sole source file is an
assembly one), and it being a dump test glibc also shouldn't matter.
Attached the (gzip-ed) binary that I've reproduced using the ld
options logged and the object file found in ld/tmpdir/. It clearly
shows that the processor-specific program header comes first, which
is what is causing the test to fail (from all I can tell).
Jan
[-- Attachment #2: seg-2.gz --]
[-- Type: application/x-gzip, Size: 14952 bytes --]
prev parent reply other threads:[~2022-02-11 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 12:37 Jan Beulich
2022-02-11 5:56 ` Nelson Chu
2022-02-11 9:50 ` Jan Beulich [this message]
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=9848e976-ae7f-0644-18a7-f085ecd6228d@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=jim.wilson.gcc@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=nelson.chu@sifive.com \
--cc=palmer@rivosinc.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).