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

[David Spickett via Phabricator via llvm-commits]

DavidSpickett added a comment.

There is one reference in llvm to `arm64-pc-windows-msvc` (llvm/test/tools/llvm-lib/Inputs/arm64.ll) so I assume there is some mapping between arm64 -> aarch64 naming. So perhaps "arm64ec-pc-windows" like Apple has "arm64e-apple-darwin"? Internally converted to aarch64ec-pc-windows-msvc. Is there a big reason to put the EC bit on the end?

(I am fuzzy on the rules, if any for tripples/quadruples)

> Another potential option could be to use subarches, like is done in apple toolchains, for selecting different ABIs within the same architecture, like armv7k and arm64e there. I presume that blocks using that field for finer details, like armv8.5a though (not sure how common that is).

Finer details I'd expect to be specified by `-march` or `-mcpu`. Though we do handle things like "thumbv7" vs "thumbv8" which is a similar kind of detail (you could `-mthumb -march=armv(7|8)-a` instead).


Repository:
  rG LLVM Github Monorepo

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

https://reviews.llvm.org/D125412