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
Copy file name to clipboardExpand all lines: README.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -299,6 +299,11 @@ Leave out to test the CPU backend:
299
299
$> julia -e 'import Pkg; Pkg.test("AcceleratedKernels.jl")'
300
300
```
301
301
302
+
Start Julia with multiple threads to run the tests on a multithreaded CPU backend:
303
+
```bash
304
+
$> julia --threads=4 -e 'import Pkg; Pkg.test("AcceleratedKernels.jl")'
305
+
```
306
+
302
307
303
308
## 8. Issues and Debugging
304
309
As the compilation pipeline of GPU kernels is different to that of base Julia, error messages also look different - for example, where Julia would insert an exception when a variable name was not defined (e.g. we had a typo), a GPU kernel throwing exceptions cannot be compiled and instead you'll see some cascading errors like `"[...] compiling [...] resulted in invalid LLVM IR"` caused by `"Reason: unsupported use of an undefined name"` resulting in `"Reason: unsupported dynamic function invocation"`, etc.
0 commit comments