rust/compiler/rustc_target/src/spec/aarch64_unknown_netbsd.rs

use crate::spec::{Target, TargetOptions};

pub fn target() -> Target {
    Target {
        llvm_target: "aarch64-unknown-netbsd".into(),
        pointer_width: 64,
        data_layout: "e-m:e-i8:8:32-i16:16:32-i64:64-i128:128-n32:64-S128".into(),
        arch: "aarch64".into(),
        options: TargetOptions {
            mcount: "__mcount".into(),
            max_atomic_width: Some(128),
            ..super::netbsd_base::opts()
        },
    }
}
rustc_target: Move `linker_flavor` from `Target` to `TargetOptions` 2020-10-08 19:22:28 +00:00			`use crate::spec::{Target, TargetOptions};`
Add aarch64-unknown-netbsd target 2018-08-04 21:53:52 +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 12:37:55 +00:00			`pub fn target() -> Target {`
			`Target {`
Replace every `String` in Target(Options) with `Cow<'static, str>` 2022-03-22 10:43:05 +00:00			`llvm_target: "aarch64-unknown-netbsd".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 16:08:12 +00:00			`pointer_width: 64,`
Replace every `String` in Target(Options) with `Cow<'static, str>` 2022-03-22 10:43:05 +00:00			`data_layout: "e-m:e-i8:8:32-i16:16:32-i64:64-i128:128-n32:64-S128".into(),`
			`arch: "aarch64".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 11:22:13 +00:00			`options: TargetOptions {`
Replace every `String` in Target(Options) with `Cow<'static, str>` 2022-03-22 10:43:05 +00:00			`mcount: "__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 11:22:13 +00:00			`max_atomic_width: Some(128),`
			`..super::netbsd_base::opts()`
			`},`
rustc_target: Refactor away `TargetResult` Construction of a built-in target is always infallible now, so `TargetResult` is no longer necessary. 2020-10-05 12:37:55 +00:00			`}`
Add aarch64-unknown-netbsd target 2018-08-04 21:53:52 +00:00			`}`