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

Rollup merge of #114826 - xzmeng:fix-typos, r=JohnTitor

Browse Source 
Fix typos
This commit is contained in:
Matthias Krüger 2023-08-15 20:34:25 +02:00 committed by GitHub
commit fa15f94e42
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
6 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/doc/rustc/src/codegen-options/index.md
View File

@ -584,7 +584,7 @@ See the [Symbol Mangling] chapter for details on symbol mangling and the manglin
This instructs `rustc` to generate code specifically for a particular processor.
You can run `rustc --print target-cpus` to see the valid options to pass
and the default target CPU for the current buid target.
and the default target CPU for the current build target.
Each target has a default base CPU. Special values include:
* `native` can be passed to use the processor of the host machine.

2
src/doc/rustc/src/platform-support/aarch64-unknown-teeos.md
View File

@ -10,7 +10,7 @@ It's very small that there is no RwLock, no network, no stdin, and no file syste
Some abbreviation:
| Abbreviation | The full text | Description |
| ---- | ---- | ---- |
| TEE | Trusted Execution Environment | ARM TrustZone devide the system into two worlds/modes -- the secure world/mode and the normal world/mode. TEE is in the secure world/mode. |
| TEE | Trusted Execution Environment | ARM TrustZone divides the system into two worlds/modes -- the secure world/mode and the normal world/mode. TEE is in the secure world/mode. |
| REE | Rich Execution Environment | The normal world. for example, Linux for Android phone is in REE side. |
| TA | Trusted Application | The app run in TEE side system. |
| CA | Client Application | The progress run in REE side system. |

2
src/doc/rustc/src/platform-support/loongarch-linux.md
View File

@ -71,7 +71,7 @@ CXX_loongarch64_unknown_linux_gnu=/TOOLCHAIN_PATH/bin/loongarch64-unknown-linux-
AR_loongarch64_unknown_linux_gnu=/TOOLCHAIN_PATH/bin/loongarch64-unknown-linux-gnu-gcc-ar \
CARGO_TARGET_LOONGARCH64_UNKNOWN_LINUX_GNUN_LINKER=/TOOLCHAIN_PATH/bin/loongarch64-unknown-linux-gnu-gcc \
# SET TARGET SYSTEM LIBRARY PATH
CARGO_TARGET_LOONGARCH64_UNKNOWN_LINUX_GNUN_RUNNER="qemu-loongarch64 -L /TOOLCHAIN_PATH/TARGET_LIBRAY_PATH" \
CARGO_TARGET_LOONGARCH64_UNKNOWN_LINUX_GNUN_RUNNER="qemu-loongarch64 -L /TOOLCHAIN_PATH/TARGET_LIBRARY_PATH" \
cargo run --target loongarch64-unknown-linux-gnu --release
```
Tested on x86 architecture, other architectures not tested.

2
src/doc/rustc/src/platform-support/netbsd.md
View File

@ -86,7 +86,7 @@ The Rust testsuite could presumably be run natively.
For the systems where the maintainer can build natively, the rust
compiler itself is re-built natively. This involves the rust compiler
being re-built with the newly self-built rust compiler, so excercises
being re-built with the newly self-built rust compiler, so exercises
the result quite extensively.
Additionally, for some systems we build `librsvg`, and for the more

4
src/doc/rustc/src/platform-support/x86_64h-apple-darwin.md
View File

@ -20,7 +20,7 @@ will fail to load on machines that do not support this.
It should support the full standard library (`std` and `alloc` either with
default or user-defined allocators). This target is probably most useful when
targetted via cross-compilation (including from `x86_64-apple-darwin`), but if
targeted via cross-compilation (including from `x86_64-apple-darwin`), but if
built manually, the host tools work.
It is similar to `x86_64-apple-darwin` in nearly all respects, although the
@ -49,7 +49,7 @@ suite seems to work.
Cross-compilation to this target from Apple hosts should generally work without
much configuration, so long as XCode and the CommandLineTools are installed.
Targetting it from non-Apple hosts is difficult, but no moreso than targetting
Targeting it from non-Apple hosts is difficult, but no more so than targeting
`x86_64-apple-darwin`.
When compiling C code for this target, either the "`x86_64h-apple-macosx*`" LLVM

2
src/doc/unstable-book/src/compiler-flags/path-options.md
View File

@ -1,6 +1,6 @@
# `--print` Options
The behavior of the `--print` flag can be modified by optionally be specifiying a filepath
The behavior of the `--print` flag can be modified by optionally be specifying a filepath
for each requested information kind, in the format `--print KIND=PATH`, just like for
`--emit`. When a path is specified, information will be written there instead of to stdout.