ahmed/OpenCL-CTS
1
0
Fork 0
mirror of https://github.com/KhronosGroup/OpenCL-CTS.git synced 2026-03-19 06:09:01 +00:00
Code Issues Packages Projects Releases Wiki Activity

[NFC] README.md: fix typos (#1704)

Browse Source 
Signed-off-by: Sven van Haastregt <sven.vanhaastregt@arm.com>
This commit is contained in:
Sven van Haastregt
2023-04-24 11:39:27 +01:00
committed by GitHub
parent 4f5af72088
commit b57445e56a
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@@ -1,6 +1,6 @@
# OpenCL Conformance Test Suite (CTS) # OpenCL Conformance Test Suite (CTS)
This it the OpenCL CTS for all versions of the Khronos This is the OpenCL CTS for all versions of the Khronos
[OpenCL](https://www.khronos.org/opencl/) standard. [OpenCL](https://www.khronos.org/opencl/) standard.
## Building the CTS ## Building the CTS
@@ -89,7 +89,7 @@ require compilation, these are:
## Generating a Conformance Report ## Generating a Conformance Report
The Khronos [Conformance Process Document](https://members.khronos.org/document/dl/911) The Khronos [Conformance Process Document](https://members.khronos.org/document/dl/911)
details the steps required for a conformance submissions. details the steps required for a conformance submission.
In this repository [opencl_conformance_tests_full.csv](test_conformance/submission_details_template.txt) In this repository [opencl_conformance_tests_full.csv](test_conformance/submission_details_template.txt)
defines the full list of tests which must be run for conformance. The output log defines the full list of tests which must be run for conformance. The output log
of which must be included alongside a filled in of which must be included alongside a filled in
@@ -105,7 +105,7 @@ the version of the repository conformance submissions are made against.
Contributions are welcome to the project from Khronos members and non-members Contributions are welcome to the project from Khronos members and non-members
alike via GitHub Pull Requests (PR). Alternatively, if you've found a bug or have alike via GitHub Pull Requests (PR). Alternatively, if you've found a bug or have
a questions please file an issue in the GitHub project. First time contributors a question please file an issue in the GitHub project. First time contributors
will be required to sign the Khronos Contributor License Agreement (CLA) before will be required to sign the Khronos Contributor License Agreement (CLA) before
their PR can be merged. their PR can be merged.