[PATCH] D125412: [ARM64EC 2/?] Add target triple, and allow targeting it.

Eli Friedman via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Thu May 12 10:56:08 PDT 2022


efriedma added a comment.

> If we'd want to use this ABI mode for mingw targets too [...], I guess that would have to be another separate target like ...-gnu_arm64ec - using up yet another entry in enum EnvironmentType for it.

Yes, you'd have to do something like that.

We could do something like arm64ec-pc-windows-msvc, I guess.  That sort of goes against the spirit of target triples: the first part is usually used to describe the instruction set, and the fourth part is usually used to describe alternate ABI/environment/etc.  It's not like "arm64ec" makes sense anywhere other than Windows, anyway.

Of course, everything related to triples is a bit fuzzy; if we want to use AArch64SubArch_arm64ec, there isn't really anything stopping us.

> (not quite sure right now if it's doable and something that one wants to do at some point, or if it ties in to too many other MSVC specifics),

Not sure if I'm going to end up hooking up ARM64EC support in lld.  And I'm not sure if any of the runtime libraries need to be linked in statically.  Otherwise, I don't see any reason you couldn't add support to mingw.

> I presume that blocks using that field for finer details, like armv8.5a though (not sure how common that is).

We don't really do that sort of thing on aarch64, only 32-bit ARM.  See also parseSubArch() in Triple.cpp.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D125412/new/

https://reviews.llvm.org/D125412



More information about the llvm-commits mailing list