diff options
| author | Jack O'Connor <[email protected]> | 2021-02-18 15:34:34 -0500 |
|---|---|---|
| committer | Jack O'Connor <[email protected]> | 2021-02-18 15:34:40 -0500 |
| commit | 1074f02d57596fe3fa70648d1fdccc3efefcd169 (patch) | |
| tree | b9eabb5a0e90b5167cdff436000d75b068df7fee | |
| parent | e2ae3bdd940b4c9778adc4a300514104fac44aa1 (diff) | |
clarify C build instructions a bit
| -rw-r--r-- | c/README.md | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/c/README.md b/c/README.md index d4d4b7c..8428e48 100644 --- a/c/README.md +++ b/c/README.md @@ -181,13 +181,13 @@ widest instruction set available. By default, `blake3_dispatch.c` expects to be linked with code for five different instruction sets: portable C, SSE2, SSE4.1, AVX2, and AVX-512. -For each of the x86 SIMD instruction sets, two versions are available, -one in assembly (which is further divided into three flavors: Unix, -Windows MSVC, and Windows GNU) and one using C intrinsics. The assembly -versions are generally preferred: they perform better, they perform more -consistently across different compilers, and they build more quickly. On -the other hand, the assembly versions are x86\_64-only, and you need to -select the right flavor for your target platform. +For each of the x86 SIMD instruction sets, four versions are available: +three flavors of assembly (Unix, Windows MSVC, and Windows GNU) and one +version using C intrinsics. The assembly versions are generally +preferred. They perform better, they perform more consistently across +different compilers, and they build more quickly. On the other hand, the +assembly versions are x86\_64-only, and you need to select the right +flavor for your target platform. Here's an example of building a shared library on x86\_64 Linux using the assembly implementations: |