-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
6 changed files
with
67 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
27 changes: 27 additions & 0 deletions
27
compiler/rustc_target/src/spec/targets/arm64e_apple_darwin.rs
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
use super::apple_base::{macos_llvm_target, opts, Arch}; | ||
use crate::spec::{FramePointer, SanitizerSet, Target, TargetOptions}; | ||
|
||
pub fn target() -> Target { | ||
let arch = Arch::Arm64e; | ||
let mut base = opts("macos", arch); | ||
base.cpu = "apple-m1".into(); | ||
base.max_atomic_width = Some(128); | ||
|
||
// FIXME: The leak sanitizer currently fails the tests, see #88132. | ||
base.supported_sanitizers = SanitizerSet::ADDRESS | SanitizerSet::CFI | SanitizerSet::THREAD; | ||
|
||
Target { | ||
// Clang automatically chooses a more specific target based on | ||
// MACOSX_DEPLOYMENT_TARGET. To enable cross-language LTO to work | ||
// correctly, we do too. | ||
llvm_target: macos_llvm_target(arch).into(), | ||
pointer_width: 64, | ||
data_layout: "e-m:o-i64:64-i128:128-n32:64-S128".into(), | ||
arch: arch.target_arch(), | ||
options: TargetOptions { | ||
mcount: "\u{1}mcount".into(), | ||
frame_pointer: FramePointer::NonLeaf, | ||
..base | ||
}, | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
# `arm64e-apple-darwin` | ||
|
||
**Tier: 3 (with Host Tools)** | ||
|
||
ARM64e macOS (11.0+, Big Sur+) | ||
|
||
## Target maintainers | ||
|
||
- Artyom Tetyukhin ([@arttet](https://github.com/https://github.com/arttet)) | ||
|
||
## Requirements | ||
|
||
Target for `macOS` on late-generation `M` series Apple chips. | ||
|
||
## Building the target | ||
|
||
You can build Rust with support for the targets by adding it to the `target` list in `config.toml`: | ||
|
||
```toml | ||
[build] | ||
target = [ "arm64e-apple-darwin" ] | ||
``` | ||
|
||
## Building Rust programs | ||
|
||
Rust does not yet ship pre-compiled artifacts for this target. | ||
To compile for this target, you will need to build Rust with the target enabled (see [Building the target](#building-the-target) above). | ||
|
||
## Testing | ||
|
||
The target does support running binaries on macOS platforms with `arm64e` architecture. | ||
|
||
## Cross-compilation toolchains and C code | ||
|
||
The targets do support `C` code. | ||
To build compatible `C` code, you have to use XCode with the same compiler and flags. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters