From: Tamar Christina <Tamar.Christina@arm.com>
To: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>,
NightStrike <nightstrike@gmail.com>,
Mark Harmstone <mark@harmstone.com>
Cc: "wej22007@outlook.com" <wej22007@outlook.com>,
"zac.walker@linaro.org" <zac.walker@linaro.org>,
binutils <binutils@sourceware.org>,
"nickc@redhat.com" <nickc@redhat.com>
Subject: RE: [PATCH 1/8] ld: Rename aarch64pe emulation target to arm64pe
Date: Tue, 3 Jan 2023 14:14:09 +0000 [thread overview]
Message-ID: <VI1PR08MB532502D79437DF97A75A9329FFF49@VI1PR08MB5325.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <01e2b3d2-ad18-27ba-9761-82d2d521c00e@foss.arm.com>
> -----Original Message-----
> From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
> Sent: Tuesday, January 3, 2023 2:09 PM
> To: Tamar Christina <Tamar.Christina@arm.com>; NightStrike
> <nightstrike@gmail.com>; Mark Harmstone <mark@harmstone.com>
> Cc: wej22007@outlook.com; zac.walker@linaro.org; binutils
> <binutils@sourceware.org>; nickc@redhat.com
> Subject: Re: [PATCH 1/8] ld: Rename aarch64pe emulation target to arm64pe
>
> On 03/01/2023 12:09, Tamar Christina via Binutils wrote:
> > Unfortunately I don’t think it’s that simple..
> >
> > Sadly the name Arm64 is the one Microsoft has chosen to call their target
> ABI. https://learn.microsoft.com/en-us/windows/arm/overview Further
> this is extended to Arm64EC etc https://learn.microsoft.com/en-
> us/cpp/build/arm64-windows-abi-conventions?view=msvc-170.
> >
> > So even though this is not the official naming that Arm uses, it’s
> > however the official one on Windows and so it’s reasonable that the PE
> target in LD follow this.
> >
> > So this is reasonable so long as the actual target itself stays aarch64-little.
> >
> > Kind Regards,
> > Tamar
> >
> > From: NightStrike <nightstrike@gmail.com>
> > Sent: Tuesday, January 3, 2023 12:00 PM
> > To: Mark Harmstone <mark@harmstone.com>
> > Cc: wej22007@outlook.com; zac.walker@linaro.org; Tamar Christina
> > <Tamar.Christina@arm.com>; binutils <binutils@sourceware.org>
> > Subject: Re: [PATCH 1/8] ld: Rename aarch64pe emulation target to
> > arm64pe
> >
> >
> > On Thu, Dec 29, 2022, 21:41 Mark Harmstone
> <mark@harmstone.com<mailto: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.
>
> The problem with arm64 is that it also matches existing configure scripts that
> use arm* for the 32-bit targets. I don't think this is a good idea. GNU tools
> have consistently used the official name for all targets.
>
But the proposal here isn't to rename the target itself to arm64, only the emulation name.
I.e. only when you explicitly use -m, The target itself stays aarch64-* so this shouldn't break any
configure though. But it will at least be consistent with the existing platform tools, of which binutils
is the last to the party.
Regards,
Tamar
> R.
>
next prev parent reply other threads:[~2023-01-03 14:14 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 [this message]
2023-01-03 12:53 ` Martin Storsjö
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=VI1PR08MB532502D79437DF97A75A9329FFF49@VI1PR08MB5325.eurprd08.prod.outlook.com \
--to=tamar.christina@arm.com \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=binutils@sourceware.org \
--cc=mark@harmstone.com \
--cc=nickc@redhat.com \
--cc=nightstrike@gmail.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).