bjoernager/rust
bjoernager/rust
1
Fork 0
Code Activity
rust/compiler/rustc_target/src/spec/aarch64_unknown_linux_gnu.rs

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

25 lines
848 B
Rust
Raw Normal View History

Maintain supported sanitizers as a target property This commit adds an additional target property – `supported_sanitizers`, and replaces the hardcoded allowlists in argument parsing to use this new property. Fixes #81802
2021-02-08 00:49:00 +02:00
use crate::spec::{SanitizerSet, Target, TargetOptions};
Initial version of AArch64 support. Adds AArch64 knowledge to: * configure, * make files, * sources, * tests, and * documentation.
2014-12-12 23:39:27 +00:00
rustc_target: Refactor away `TargetResult` Construction of a built-in target is always infallible now, so `TargetResult` is no longer necessary.
2020-10-05 15:37:55 +03:00
pub fn target() -> Target {
Target {
Replace every `String` in Target(Options) with `Cow<'static, str>`
2022-03-22 11:43:05 +01:00
llvm_target: "aarch64-unknown-linux-gnu".into(),
Use integer literals for builtin target_pointer_width fields Also change target_pointer_width to pointer_width. Preparation for a subsequent type change of target_pointer_width to an integer together with a rename to pointer_width. On its own, this commit breaks the build. I don't like making build-breaking commits, but in this instance I believe that it makes review easier, as the "real" changes of this PR can be seen much more easily. Result of running: find compiler/rustc_target/src/spec/ -type f -exec sed -i -e 's/target_pointer_width: "\(.*\)"\..*,/pointer_width: \1,/g' {} \;
2020-10-14 18:08:12 +02:00
pointer_width: 64,
Replace every `String` in Target(Options) with `Cow<'static, str>`
2022-03-22 11:43:05 +01:00
data_layout: "e-m:e-i8:8:32-i16:16:32-i64:64-i128:128-n32:64-S128".into(),
arch: "aarch64".into(),
check target abi support
2016-10-24 11:04:04 +02:00
options: TargetOptions {
Replace every `String` in Target(Options) with `Cow<'static, str>`
2022-03-22 11:43:05 +01:00
features: "+outline-atomics".into(),
mcount: "\u{1}_mcount".into(),
Replace per-target ABI denylist with an allowlist It makes very little sense to maintain denylists of ABIs when, as far as non-generic ABIs are concerned, targets usually only support a small subset of the available ABIs. This has historically been a cause of bugs such as us allowing use of the platform-specific ABIs on x86 targets – these in turn would cause LLVM errors or assertions to fire. Fixes #57182 Sponsored by: standard.ai
2021-06-11 14:22:13 +03:00
max_atomic_width: Some(128),
supported_sanitizers: SanitizerSet::ADDRESS
Add LLVM CFI support to the Rust compiler This commit adds LLVM Control Flow Integrity (CFI) support to the Rust compiler. It initially provides forward-edge control flow protection for Rust-compiled code only by aggregating function pointers in groups identified by their number of arguments. Forward-edge control flow protection for C or C++ and Rust -compiled code "mixed binaries" (i.e., for when C or C++ and Rust -compiled code share the same virtual address space) will be provided in later work as part of this project by defining and using compatible type identifiers (see Type metadata in the design document in the tracking issue #89653). LLVM CFI can be enabled with -Zsanitizer=cfi and requires LTO (i.e., -Clto).
2021-10-07 15:33:13 -07:00
| SanitizerSet::CFI
Replace per-target ABI denylist with an allowlist It makes very little sense to maintain denylists of ABIs when, as far as non-generic ABIs are concerned, targets usually only support a small subset of the available ABIs. This has historically been a cause of bugs such as us allowing use of the platform-specific ABIs on x86 targets – these in turn would cause LLVM errors or assertions to fire. Fixes #57182 Sponsored by: standard.ai
2021-06-11 14:22:13 +03:00
| SanitizerSet::LEAK
| SanitizerSet::MEMORY
MemTagSanitizer Support Adds support for the LLVM MemTagSanitizer.
2021-12-03 16:11:13 -05:00
| SanitizerSet::MEMTAG
Replace per-target ABI denylist with an allowlist It makes very little sense to maintain denylists of ABIs when, as far as non-generic ABIs are concerned, targets usually only support a small subset of the available ABIs. This has historically been a cause of bugs such as us allowing use of the platform-specific ABIs on x86 targets – these in turn would cause LLVM errors or assertions to fire. Fixes #57182 Sponsored by: standard.ai
2021-06-11 14:22:13 +03:00
| SanitizerSet::THREAD
| SanitizerSet::HWADDRESS,
XRay support flag in TargetOptions Specify where XRay is supported. I only test ARM64 and x86_64, but hey those others should work too, right? LLVM documentation says that MIPS and PPC are also supported, but I don't have the hardware, so I won't pretend. Naturally, more targets can be added later with more testing.
2022-10-02 10:45:54 +09:00
supports_xray: true,
Replace per-target ABI denylist with an allowlist It makes very little sense to maintain denylists of ABIs when, as far as non-generic ABIs are concerned, targets usually only support a small subset of the available ABIs. This has historically been a cause of bugs such as us allowing use of the platform-specific ABIs on x86 targets – these in turn would cause LLVM errors or assertions to fire. Fixes #57182 Sponsored by: standard.ai
2021-06-11 14:22:13 +03:00
..super::linux_gnu_base::opts()
check target abi support
2016-10-24 11:04:04 +02:00
},
rustc_target: Refactor away `TargetResult` Construction of a built-in target is always infallible now, so `TargetResult` is no longer necessary.
2020-10-05 15:37:55 +03:00
}
Initial version of AArch64 support. Adds AArch64 knowledge to: * configure, * make files, * sources, * tests, and * documentation.
2014-12-12 23:39:27 +00:00
}
Copy permalink