Rollup merge of #97201 - ydah:fix_spelling, r=GuillaumeGomez
Fix typo This PR is fixes typo "avaiable" to "available".
This commit is contained in:
commit
35986cd1fb
@ -4,7 +4,7 @@
|
||||
|
||||
Windows targets similar to `*-pc-windows-gnu` but using UCRT as the runtime and various LLVM tools/libraries instead of GCC/Binutils.
|
||||
|
||||
Target triples avaiable so far:
|
||||
Target triples available so far:
|
||||
- `aarch64-pc-windows-gnullvm`
|
||||
- `x86_64-pc-windows-gnullvm`
|
||||
|
||||
@ -26,7 +26,7 @@ Like with any other Windows target created binaries are in PE format.
|
||||
## Building the target
|
||||
|
||||
For cross-compilation I recommend using [llvm-mingw](https://github.com/mstorsjo/llvm-mingw) toolchain, one change that seems necessary beside configuring corss compilers is disabling experimental `m86k` target. Otherwise LLVM build fails with `multiple definition ...` errors.
|
||||
Native bootstrapping builds require rather fragile hacks until host artifacts are avaiable so I won't describe them here.
|
||||
Native bootstrapping builds require rather fragile hacks until host artifacts are available so I won't describe them here.
|
||||
|
||||
## Building Rust programs
|
||||
|
||||
|
@ -3,7 +3,7 @@
|
||||
//! The features are detected using the `detect_features` function below.
|
||||
//! This function uses the CPUID instruction to read the feature flags from the
|
||||
//! CPU and encodes them in a `usize` where each bit position represents
|
||||
//! whether a feature is available (bit is set) or unavaiable (bit is cleared).
|
||||
//! whether a feature is available (bit is set) or unavailable (bit is cleared).
|
||||
//!
|
||||
//! The enum `Feature` is used to map bit positions to feature names, and the
|
||||
//! the `__crate::detect::check_for!` macro is used to map string literals (e.g.,
|
||||
|
@ -3,7 +3,7 @@
|
||||
//! The features are detected using the `detect_features` function below.
|
||||
//! This function uses the CPUID instruction to read the feature flags from the
|
||||
//! CPU and encodes them in a `usize` where each bit position represents
|
||||
//! whether a feature is available (bit is set) or unavaiable (bit is cleared).
|
||||
//! whether a feature is available (bit is set) or unavailable (bit is cleared).
|
||||
//!
|
||||
//! The enum `Feature` is used to map bit positions to feature names, and the
|
||||
//! the `__crate::detect::check_for!` macro is used to map string literals (e.g.,
|
||||
|
Loading…
Reference in New Issue
Block a user