mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fixed some typographical errors in arm-none-eabi.md.

Browse Source
This commit is contained in:
Jonathan Pallant 2024-04-26 15:54:27 +01:00
parent b0f75628d2
commit b17398490b
No known key found for this signature in database
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/doc/rustc/src/platform-support/arm-none-eabi.md
View File

@ -43,7 +43,7 @@ FPU support.
If a target ends if `eabihf`, that target uses the so-called *hard-float ABI*: 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 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 minimum support FPU for that architecture is available. More advanced FPU
instructions (e.g. ones that work on double-precision `f64` values) may be 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 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. in the detailed target-specific documentation.
**Note:** Many target-features are currently unstable and subject to change, and **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. 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 them to your `.cargo/config.toml` file alongside any other flags your project
uses (likely linker related ones): uses (likely linker related ones):