From b17398490b0a6cb6b99cbf0d192e2952ae4f4b9b Mon Sep 17 00:00:00 2001 From: Jonathan Pallant Date: Fri, 26 Apr 2024 15:54:27 +0100 Subject: [PATCH] Fixed some typographical errors in arm-none-eabi.md. --- src/doc/rustc/src/platform-support/arm-none-eabi.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/doc/rustc/src/platform-support/arm-none-eabi.md b/src/doc/rustc/src/platform-support/arm-none-eabi.md index de41c5e676a..4bd1d68fb75 100644 --- a/src/doc/rustc/src/platform-support/arm-none-eabi.md +++ b/src/doc/rustc/src/platform-support/arm-none-eabi.md @@ -43,7 +43,7 @@ FPU support. If a target ends if `eabihf`, that target uses the so-called *hard-float ABI*: functions which take `f32` or `f64` as arguments will have them passed via FPU -registers. These target therefore require the use of an FPU and will assume the +registers. These targets therefore require the use of an FPU and will assume the minimum support FPU for that architecture is available. More advanced FPU instructions (e.g. ones that work on double-precision `f64` values) may be generated if the code is compiled with a `target-cpu` or `target-feature` option @@ -66,10 +66,10 @@ scheduling and support for the features you do have. More details are available in the detailed target-specific documentation. **Note:** Many target-features are currently unstable and subject to change, and -if you use them you should dissassmble the compiler output and manually inspect +if you use them you should disassemble the compiler output and manually inspect it to ensure only appropriate instructions for your CPU have been generated. -If do you wish to use the *target-cpu* and *target-feature* options, you can add +If you wish to use the *target-cpu* and *target-feature* options, you can add them to your `.cargo/config.toml` file alongside any other flags your project uses (likely linker related ones):