You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Improve build procedure and instructions (vosen#28)
Fixes issues pointed out in vosen#27:
* spirv_tools-sys was build in non-test profiles
* By default ZLUDA dll has a wrong name
* We relied on third-party OpenCL installation on Windows
* We encouraged building debug configuration
* We didn't provide build information for developers (cmake, python, submodules)
Copy file name to clipboardExpand all lines: README.md
+18-7Lines changed: 18 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,13 +33,13 @@ Overall in this suite of benchmarks faster by approximately 4% on ZLUDA.
33
33
## Details
34
34
35
35
* Is ZLUDA a drop-in replacement for CUDA?\
36
-
Yes, but certain applications use CUDA in ways which make it incompatible with ZLUDA.
37
-
* What is the status of the project\
36
+
Yes, but certain applications use CUDA in ways which make it incompatible with ZLUDA
37
+
* What is the status of the project?\
38
38
This project is a Proof of Concept. About the only thing that works currently is Geekbench (and not even completely). It's amazingly buggy and incomplete. You should not rely on it for anything serious
39
39
* Is it an Intel project? Is it an NVIDIA project?\
40
40
No, it's a private project
41
41
* What is the performance?\
42
-
Performance can be clode to the performance of similarly written OpenCL code (see GeekBench results in the previous section). NVIDIA GPUs and Intel GPUs have different architecture and feature set. Consequently, certain NVIDIA features have to be emulated in ZLUDA with performance penalty. Additionally, performance of ZLUDA will be always lower than the performance of code specifically optimized for Intel GPUs
42
+
Performance can be close to the performance of similarly written OpenCL code (see GeekBench results in the previous section). NVIDIA GPUs and Intel GPUs have different architecture and feature set. Consequently, certain NVIDIA features have to be emulated in ZLUDA with performance penalty. Additionally, performance of ZLUDA will be always lower than the performance of code specifically optimized for Intel GPUs
43
43
* How it's different from AMD HIP or Intel DPC++ Compatibility toolkit?\
44
44
Both are porting toolkits which require programmer's effort to port applications to the API in question. With ZLUDA existing applications "just work" on an Intel GPU (if you are lucky and ZLUDA supports the particular subset of CUDA)
45
45
* Which Intel GPU are supported?\
@@ -52,11 +52,11 @@ Overall in this suite of benchmarks faster by approximately 4% on ZLUDA.
52
52
**Warning**: this is a very incomplete Proof of Concept. It's probably not going to work with your application. ZLUDA currently works only with applications which use CUDA Driver API. Linux builds also work with applications which use statically-linked CUDA Runtime API
53
53
54
54
### Windows
55
-
You should have the most recent GPU drivers installed.\
55
+
You should have the most recent Intel GPU drivers installed.\
56
56
Copy `nvcuda.dll` to the application directory (the directory where .exe file is) and launch it normally
57
57
58
58
### Linux
59
-
A very recent version of [compute-runtime](https://github.com/intel/compute-runtime) is required. At the time of the writing 20.45.18403 is the recommended version.
59
+
A very recent version of [compute-runtime](https://github.com/intel/compute-runtime)and [Level Zero loader](https://github.com/oneapi-src/level-zero/releases)is required. At the time of the writing 20.45.18403 is the losest recommended version.
60
60
Unpack the archive somewhere and run your application like this:
0 commit comments