From: "Martin Storsjö" <martin@martin.st>
To: NightStrike <nightstrike@gmail.com>
Cc: Mark Harmstone <mark@harmstone.com>,
wej22007@outlook.com, zac.walker@linaro.org,
tamar.christina@arm.com, binutils <binutils@sourceware.org>
Subject: Re: [PATCH 1/8] ld: Rename aarch64pe emulation target to arm64pe
Date: Tue, 3 Jan 2023 14:53:24 +0200 (EET) [thread overview]
Message-ID: <513db747-c89c-85f3-dc29-13ab8cfcceba@martin.st> (raw)
In-Reply-To: <CAF1jjLsxDUx0FRKXs3zhRVMs=RokYoAbQRbQaDbZJtWOM5MmUA@mail.gmail.com>
On Tue, 3 Jan 2023, NightStrike via Binutils wrote:
> On Thu, Dec 29, 2022, 21:41 Mark Harmstone <mark@harmstone.com> wrote:
>
>> * The aarch64pe emulation target is renamed to arm64pe. This is the name
>> that LLVM is already using, even though as a rule we call this arch
>> aarch64.
>> Without this clang won't work with ld. Another possibility would be to
>> change the -m parameter if it's "arm64", but that seems to me like it's
>> making things more complicated than they need to be.
>>
>
> Or just fix clang. Seems like if clang wants to work with ld, clang should
> use ld's name.
When lld added the "arm64pe" target in the mingw mode of lld, 5 years ago,
there was no support for such a target in binutils ld. That support is
being added now.
Therefore - there was no reference for what to name this particular target
in the ld.bfd like interface mode - so I picked one name which seemed to
make sense for it - "arm64pe". Now when binutils is catching up 5 years
later, I think it's courteous to go along with the name that was picked
within lld for this mode.
// Martin
prev parent reply other threads:[~2023-01-03 12:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 2:40 Mark Harmstone
2022-12-30 2:40 ` [PATCH 2/8] Fix size of external_reloc for pe-aarch64 Mark Harmstone
2022-12-30 2:40 ` [PATCH 3/8] Skip ELF-specific tests when targeting pe-aarch64 Mark Harmstone
2022-12-30 2:40 ` [PATCH 4/8] Skip big-obj test for pe-aarch64 Mark Harmstone
2022-12-30 2:40 ` [PATCH 5/8] Add pe-aarch64 relocations Mark Harmstone
2022-12-30 2:40 ` [PATCH 6/8] Add .secrel32 for pe-aarch64 Mark Harmstone
2022-12-30 2:40 ` [PATCH 7/8] Add aarch64-w64-mingw32 target Mark Harmstone
2022-12-30 2:40 ` [PATCH 8/8] gas: Restore tc_pe_dwarf2_emit_offset for pe-aarch64 Mark Harmstone
2023-01-03 11:54 ` [PATCH 1/8] ld: Rename aarch64pe emulation target to arm64pe Nick Clifton
2023-01-03 11:59 ` NightStrike
2023-01-03 12:09 ` Tamar Christina
2023-01-03 14:08 ` Richard Earnshaw
2023-01-03 14:13 ` Martin Storsjö
2023-01-03 14:54 ` Tamar Christina
2023-01-03 15:51 ` Martin Storsjö
2023-01-03 15:57 ` Tamar Christina
2023-01-03 18:21 ` Mark Harmstone
2023-01-03 18:33 ` Andrew Pinski
2023-01-03 19:07 ` Mark Harmstone
2023-01-03 19:41 ` Tamar Christina
2023-01-03 20:05 ` Martin Storsjö
2023-01-04 2:38 ` Mark Harmstone
2023-01-04 9:51 ` Nick Clifton
2023-01-04 10:25 ` Martin Storsjö
2023-01-04 10:35 ` Tamar Christina
2023-01-04 11:00 ` Martin Storsjö
2023-01-04 11:08 ` Tamar Christina
2023-01-04 11:36 ` Martin Storsjö
2023-01-04 15:02 ` Nick Clifton
2023-01-05 2:33 ` Mark Harmstone
2023-01-05 11:01 ` Nick Clifton
2023-01-05 10:45 ` Tamar Christina
2023-01-03 14:14 ` Tamar Christina
2023-01-03 12:53 ` Martin Storsjö [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=513db747-c89c-85f3-dc29-13ab8cfcceba@martin.st \
--to=martin@martin.st \
--cc=binutils@sourceware.org \
--cc=mark@harmstone.com \
--cc=nightstrike@gmail.com \
--cc=tamar.christina@arm.com \
--cc=wej22007@outlook.com \
--cc=zac.walker@linaro.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).