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: src/offload/usage.md
+14-6Lines changed: 14 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,9 @@
1
1
# Usage
2
2
3
-
This feature is work-in-progress, and not ready for usage. The instructions here are for contributors, or people interested in following the latest progress.
4
-
We currently work on launching the following Rust kernel on the GPU. To follow along, copy it to a `src/lib.rs` file.
3
+
This feature is work-in-progress, and not ready for usage.
4
+
The instructions here are for contributors, or people interested in following the latest progress.
5
+
We currently work on launching the following Rust kernel on the GPU.
It is important to use a clang compiler build on the same llvm as rustc. Just calling clang without the full path will likely use your system clang, which probably will be incompatible. So either substitute clang/lld invocations below with absolute path, or set your `PATH` accordingly.
80
+
It is important to use a clang compiler build on the same llvm as rustc.
81
+
Just calling clang without the full path will likely use your system clang, which probably will be incompatible.
82
+
So either substitute clang/lld invocations below with absolute path, or set your `PATH` accordingly.
79
83
80
-
First we generate the device (gpu) code. Replace the target-cpu with the right code for your gpu.
84
+
First we generate the device (gpu) code.
85
+
Replace the target-cpu with the right code for your gpu.
You can try to find the paths to those files on your system. However, I recommend to not fix the paths, but rather just re-generate them by copying a bare-mode openmp example and compiling it with your clang. By adding `-###` to your clang invocation, you can see the invidual steps.
98
-
It will show multiple steps, just look for the clang-linker-wrapper example. Make sure to still include the path to the `host.o` file, and not whatever tmp file you got when compiling your c++ example with the following call.
102
+
You can try to find the paths to those files on your system.
103
+
However, I recommend to not fix the paths, but rather just re-generate them by copying a bare-mode openmp example and compiling it with your clang.
104
+
By adding `-###` to your clang invocation, you can see the invidual steps.
105
+
It will show multiple steps, just look for the clang-linker-wrapper example.
106
+
Make sure to still include the path to the `host.o` file, and not whatever tmp file you got when compiling your c++ example with the following call.
99
107
```
100
108
myclang++ -fuse-ld=lld -O3 -fopenmp -fopenmp-offload-mandatory --offload-arch=gfx90a omp_bare.cpp -o main -###
0 commit comments