[libc-commits] [libc] [llvm] Refactor WIDE_READ to allow finer control over high-performance function selection (PR #165613)

[via libc-commits]

github-actions[bot] wrote:

<!--LLVM CODE FORMAT COMMENT: {clang-format}-->


:warning: C/C++ code formatter, clang-format found issues in your code. :warning:

<details>
<summary>
You can test this locally with the following command:
</summary>

``````````bash
git-clang-format --diff origin/main HEAD --extensions h -- libc/src/string/memory_utils/aarch64/inline_strlen.h libc/src/string/memory_utils/generic/inline_strlen.h libc/src/string/memory_utils/x86_64/inline_strlen.h libc/src/string/string_utils.h --diff_from_common_commit
``````````

:warning:
The reproduction instructions above might return results for more than one PR
in a stack if you are using a stacked PR workflow. You can limit the results by
changing `origin/main` to the base branch/commit you want to compare against.
:warning:

</details>

<details>
<summary>
View the diff from clang-format here.
</summary>

``````````diff
diff --git a/libc/src/string/string_utils.h b/libc/src/string/string_utils.h
index b9f020ca9..833879795 100644
--- a/libc/src/string/string_utils.h
+++ b/libc/src/string/string_utils.h
@@ -190,7 +190,7 @@ find_first_character(const unsigned char *src, unsigned char ch,
 // 3. generic - read using clang's internal vector types
 // 4. arch - hand-coded per architecture. Possibly in asm, or with intrinsics.
 //
-//The called implemenation is chosen at build-time by setting
+// The called implemenation is chosen at build-time by setting
 // LIBC_CONF_{FUNC}_IMPL in config.json
 static constexpr auto &string_length_impl =
     LIBC_COPT_STRING_LENGTH_IMPL::string_length;

``````````

</details>


https://github.com/llvm/llvm-project/pull/165613