Magic-Mirror/llvm-capstone
1
0
Fork 0
mirror of https://github.com/capstone-engine/llvm-capstone.git synced 2025-04-12 03:10:03 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

[libc][Obvious] Fix typos

Browse Source
This commit is contained in:
Cheng Wang 2021-09-04 20:14:54 +08:00
parent 650bbc5620
commit 7abd8f6c6e
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
libc/benchmarks/RATIONALE.md
View File

@ -13,7 +13,7 @@ systems; and so other metrics can be equally important:
## Rationale ## Rationale
The goal here is to satisfy the [Benchmarking The goal here is to satisfy the [Benchmarking
Principles](https://en.wikipedia.org/wiki/Benchmark_\(computing\)#Benchmarking_Principles). Principles](https://en.wikipedia.org/wiki/Benchmark_(computing)#Benchmarking_Principles).
1. **Relevance**: Benchmarks should measure relatively vital features. 1. **Relevance**: Benchmarks should measure relatively vital features.
2. **Representativeness**: Benchmark performance metrics should be broadly 2. **Representativeness**: Benchmark performance metrics should be broadly
@ -26,7 +26,7 @@ Principles](https://en.wikipedia.org/wiki/Benchmark_\(computing\)#Benchmarking_P
7. **Transparency**: Benchmark metrics should be easy to understand. 7. **Transparency**: Benchmark metrics should be easy to understand.
Benchmarking is a [subtle Benchmarking is a [subtle
art](https://en.wikipedia.org/wiki/Benchmark_\(computing\)#Challenges) and art](https://en.wikipedia.org/wiki/Benchmark_(computing)#Challenges) and
benchmarking memory functions is no exception. Here we'll dive into benchmarking memory functions is no exception. Here we'll dive into
peculiarities of designing good microbenchmarks for `llvm-libc` memory peculiarities of designing good microbenchmarks for `llvm-libc` memory
functions. functions.
@ -189,7 +189,7 @@ active cores."_
is always set to `performance`. We also want to make sure that the time based is always set to `performance`. We also want to make sure that the time based
events are not impacted by frequency scaling.** events are not impacted by frequency scaling.**
See [REAME.md](REAME.md) on how to set this up. See [README.md](README.md) on how to set this up.
### Reserved and pinned cores ### Reserved and pinned cores

2
libc/src/string/memory_utils/elements.h
View File

@ -443,7 +443,7 @@ template <size_t Size> struct Builtin {
private: private:
// Copies `kSize` bytes from `src` to `dst` using a for loop. // Copies `kSize` bytes from `src` to `dst` using a for loop.
// This code requires the use of `-fno-buitin-memcpy` to prevent the compiler // This code requires the use of `-fno-builtin-memcpy` to prevent the compiler
// from turning the for-loop back into `__builtin_memcpy`. // from turning the for-loop back into `__builtin_memcpy`.
static void ForLoopCopy(char *__restrict dst, const char *__restrict src) { static void ForLoopCopy(char *__restrict dst, const char *__restrict src) {
for (size_t i = 0; i < kSize; ++i) for (size_t i = 0; i < kSize; ++i)