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
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,9 +18,9 @@ Target codes thus-far:
18
18
This work was presented at the [HPDC 2025](https://hpdc.sci.utah.edu/2025/)[AI4Sys Workshop](https://ai4sys.github.io/).
19
19
Upon having our paper accepted, we pre-published on arXiv in case people wanted to cite us.
20
20
21
-
[paper link here](https://dl.acm.org/doi/10.1145/3731545.3743645)
21
+
📃📃 [paper link here](https://dl.acm.org/doi/10.1145/3731545.3743645)🔗🔗
22
22
23
-
BibTeX reference below.
23
+
📜 BibTeX reference below.
24
24
```
25
25
@inproceedings{10.1145/3731545.3743645,
26
26
author = {Bolet, Gregory and Georgakoudis, Giorgis and Menon, Harshitha and Parasyris, Konstantinos and Hasabnis, Niranjan and Estes, Hayden and Cameron, Kirk and Oren, Gal},
@@ -54,12 +54,12 @@ For ease-of-reproducibility, we supply a `Dockerfile` with the necessary steps t
54
54
The following is a list of steps to help you get set up and into the main bash shell of the container.
55
55
56
56
‼️‼️
57
-
We note that the base container image will take up about 40 GB of storage space; once we start building codes and gathering profiling data, the disk usage will jump up to about 50 GB.
57
+
We note that the base container image will take up about 15 GB of storage space, which then jumps to 40 GB when we build the container; once we start building codes and gathering profiling data, the disk usage will jump up to about 50 GB.
58
58
Please ensure your system has enough storage space before continuing.
@@ -116,6 +116,7 @@ By default, we have everything building with `clang++` and `clang`, this should
116
116
source ./runBuild.sh
117
117
```
118
118
NOTE: If you're running this from a Docker container generated from our Dockerfile, it should work out-of-the-box.
119
+
119
120
We originally had the CUDA codes building with `nvcc`, but to be able to also build SYCL and OMP codes, we switched to just LLVM. You may still be able to build the codes with `nvcc`, but it may take some modifications to the build pipeline.
120
121
We have future plans to sample SYCL and OMP codes, but for now, this work focuses on CUDA codes.
The scraped output will be a file called `simple-scraped-kernels-with-sass.json` in JSON format.
203
204
We particularly do this simple form of scraping because we're struggling to have a proper AST traversal script that can properly extract CUDA kernels from source.
204
205
This is a future step we're working on. For now, this file contains all the source files from each executable that was built in the `build` directory.
205
-
Because this is an update version, we include SASS code in the scrape, but these are not used in the final results of this paper.
206
+
Because this is an updated version, we include SASS code in the scrape, but these are not used in the final results of this paper.
0 commit comments