thek0tyara/llama-cpp-turboquant
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 4

Updated docs for naming

Browse source
This commit is contained in:
Alejandro Saucedo 2021-05-11 09:46:57 +01:00
parent a3db6acd5d
commit 0788ec875f
9 changed files with 29 additions and 29 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/overview/ci-tests.rst
View file

@ -2,7 +2,7 @@
CI, Docker Images, Docs & Tests
======================
This section contains an overview of the steps run on CI, as well as the tools used to simplify the testing (such as running Vulkan on CPU).
This section contains an overview of the steps run on CI, as well as the tools used to simplify the testing (such as running on CPU).
We use Github Actions to run the tests, which simplifies the workflows significantly for contributors.
@ -33,12 +33,12 @@ When submitting a PR or merging a PR into master, both of these will run - you c
Running Vulkan on the CPU
Running on the CPU
~~~~~~~~~~~~~
We use `Swiftshader <https://github.com/google/swiftshader>`_ to enable us to run the Vulkan Kompute framework directly on the CPU for the CI tests.
We use `Swiftshader <https://github.com/google/swiftshader>`_ to enable us to run the Kompute framework directly on the CPU for the CI tests.
Even though Swiftshader is optimized to function as a high-performance CPU backend for Vulkan, there are several limitations, the most notable in context of Kompute are:
Even though Swiftshader is optimized to function as a high-performance CPU backend for the Vulkan SDK, there are several limitations, the most notable in context of Kompute are:
* Loading files (spirv or text) leads to segfault
* Loading raw text string shaders leads to segfault