From: Nick Clifton <nickc@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, binutils@sourceware.org
Subject: Re: [PATCH] elf: Add is_standard_elf
Date: Fri, 26 Jan 2024 12:00:44 +0000 [thread overview]
Message-ID: <94ba2642-add9-4736-8d00-0ff24f56ec39@redhat.com> (raw)
In-Reply-To: <20240125180804.1175199-1-hjl.tools@gmail.com>
Hi H.J.
> even though PR ld/31289 targets xfail for [is_generic] targets. These
> targets not only don't use the generic_link_hash_table linker, but also
> don't use the standard ELF emulation. Add is_standard_elf for ELF
> targets which use the standard ELF emulation and replace [is_generic]
> with ![is_standard_elf] in PR ld/31289 tests.
I think that is_standard_elf might be a bit pejorative. Those targets
are conforming to the ELF standard, they are just choosing to use their
own methods for implementing it. May I instead suggest: "uses_elf_em"
as an alternative, since this seems to capture the reason for
segregating these particular targets.
Cheers
Nick
next prev parent reply other threads:[~2024-01-26 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 18:08 H.J. Lu
2024-01-26 12:00 ` Nick Clifton [this message]
2024-01-26 13:59 ` H.J. Lu
2024-04-12 10:07 ` Nick Clifton
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=94ba2642-add9-4736-8d00-0ff24f56ec39@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.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).