llvm-project.git/llvm/lib/BinaryFormat/MachO.cpp, branch users/nico/python-2 Unnamed repository; edit this file 'description' to name the repository. [AArch64][MachO] Add ptrauth ABI version to arm64e cpusubtype. (#104650) 2024-08-20T18:37:12+00:00 Ahmed Bougacha ahmed@bougacha.org 2024-08-20T18:37:12+00:00 fd4f9520a6a08c3dcf15622e3b887d8f3624fc42 In a mach_header, the cpusubtype is a 32-bit field, but it's split in 2 subfields: - the low 24 bits containing the cpu subtype proper, (e.g., CPU_SUBTYPE_ARM64E 2) - the high 8 bits containing a capability field used for additional feature flags. Notably, it's only the subtype subfield that participates in fat file slice discrimination: the caps are ignored. arm64e uses the caps subfield to encode a ptrauth ABI version: - 0x80 (CPU_SUBTYPE_PTRAUTH_ABI) denotes a versioned binary - 0x40 denotes a kernel-ABI binary - 0x00-0x0F holds the ptrauth ABI version This teaches the basic obj tools to decode that (or ignore it when unneeded). It also teaches the MachO writer to default to emitting versioned binaries, but with a version of 0 (and without the kernel ABI flag). Modern arm64e requires versioned binaries: a binary with 0x00 caps in cpusubtype is now rejected by the linker and everything after. We can live without the sophistication of specifying the version and kernel ABI for now. Co-authored-by: Francis Visoiu Mistrih <francisvm@apple.com> 
In a mach_header, the cpusubtype is a 32-bit field, but it's split in 2
subfields:
- the low 24 bits containing the cpu subtype proper, (e.g.,
CPU_SUBTYPE_ARM64E 2)
- the high 8 bits containing a capability field used for additional
feature flags.

Notably, it's only the subtype subfield that participates in fat file
slice discrimination: the caps are ignored.

arm64e uses the caps subfield to encode a ptrauth ABI version:
- 0x80 (CPU_SUBTYPE_PTRAUTH_ABI) denotes a versioned binary
- 0x40 denotes a kernel-ABI binary
- 0x00-0x0F holds the ptrauth ABI version

This teaches the basic obj tools to decode that (or ignore it when
unneeded).

It also teaches the MachO writer to default to emitting versioned
binaries, but with a version of 0 (and without the kernel ABI flag).

Modern arm64e requires versioned binaries: a binary with 0x00 caps in
cpusubtype is now rejected by the linker and everything after. We can
live without the sophistication of specifying the version and kernel ABI
for now.

Co-authored-by: Francis Visoiu Mistrih <francisvm@apple.com>
 [NFC][TargetParser] Remove llvm/ADT/Triple.h 2023-02-07T12:39:46+00:00 Archibald Elliott archibald.elliott@arm.com 2023-02-07T12:21:51+00:00 62c7f035b4392c1933550eead6ddab35122720bc I also ran `git clang-format` to get the headers in the right order for the new location, which has changed the order of other headers in two files. 
I also ran `git clang-format` to get the headers in the right order for
the new location, which has changed the order of other headers in two
files.
[NFC][TargetParser] Remove llvm/Support/ARMTargetParser.h 2023-02-07T11:05:58+00:00 Archibald Elliott archibald.elliott@arm.com 2023-02-03T14:29:12+00:00 27aeb58ce4d12e15b966dba86738eb65a96703f7 






[Triple][MachO] Define "arm64e", an AArch64 subarch for Pointer Auth.
2020-12-03T15:53:59+00:00

Ahmed Bougacha
ahmed@bougacha.org

2020-09-03T15:43:21+00:00

f77c948d56b09b839262e258af5c6ad701e5b168

This also teaches MachO writers/readers about the MachO cpu subtype,
beyond the minimal subtype reader support present at the moment.

This also defines a preprocessor macro to allow users to distinguish
__arm64__ from __arm64e__.

arm64e defaults to an "apple-a12" CPU, which supports v8.3a, allowing
pointer-authentication codegen.
It also currently defaults to ios14 and macos11.

Differential Revision: https://reviews.llvm.org/D87095





This also teaches MachO writers/readers about the MachO cpu subtype,
beyond the minimal subtype reader support present at the moment.

This also defines a preprocessor macro to allow users to distinguish
__arm64__ from __arm64e__.

arm64e defaults to an "apple-a12" CPU, which supports v8.3a, allowing
pointer-authentication codegen.
It also currently defaults to ios14 and macos11.

Differential Revision: https://reviews.llvm.org/D87095







arm64: count Triple::aarch64_32 as an aarch64 target and enable leaf frame pointers
2020-12-03T11:09:44+00:00

Tim Northover
t.p.northover@gmail.com

2020-11-10T11:15:08+00:00

152df3add156b68aca7bfb06b62ea85fa127f3b1












[MachO] Add cpu(sub)type tests and improve error handling
2020-02-24T18:44:42+00:00

Francis Visoiu Mistrih
francisvm@yahoo.com

2020-02-24T18:42:21+00:00

7b0a5683fa09be4e60bc93526aad7b63bbca687c

Add checks for triples that don't use mach-o, and unit tests for
everything.





Add checks for triples that don't use mach-o, and unit tests for
everything.







[macho][NFC] Extract all CPU_(SUB_)TYPE logic to BinaryFormat
2020-02-21T20:43:29+00:00

Francis Visoiu Mistrih
francisvm@yahoo.com

2020-02-19T00:39:05+00:00

1874dee5662603c9251228c71b66de72cec0c979

This moves all the logic of converting LLVM Triples to
MachO::CPU_(SUB_)TYPE from the specific target (Target)AsmBackend to
more convenient functions in lib/BinaryFormat.

This also gets rid of the separate two X86AsmBackend classes.

The previous attempt was to add it to libObject, but that adds an
unnecessary dependency to libObject from all the targets.

Differential Revision: https://reviews.llvm.org/D74808





This moves all the logic of converting LLVM Triples to
MachO::CPU_(SUB_)TYPE from the specific target (Target)AsmBackend to
more convenient functions in lib/BinaryFormat.

This also gets rid of the separate two X86AsmBackend classes.

The previous attempt was to add it to libObject, but that adds an
unnecessary dependency to libObject from all the targets.

Differential Revision: https://reviews.llvm.org/D74808