[SYCL][Clang] Add support for device image compression#15124
Conversation
|
Some initial performance stats: Dataset: https://github.com/aras-p/smol-v/tree/master/tests/spirv-dumps Conclusion: Note:- Most of the SPIR-V files I have in the dataset are <50KB. I'm working on extending the performance evaluation to larger workloads. Also, the (de)compression performance will vary with the format of the file being compressed, so for AOT, where device images consists of target assembly, the performance stats might differ. |
|
What happens with the PTX and AMDGPU targets? Are they covered by the "native" binary image format? Do we need additional formats? |
|
Also guessing this feature may not make sense when combined with the native cpu device, but need to think more about that. |
I think they are covered by the "none" binary image format. This is because clang driver (in SYCL offload mode) never specifies the image format in call to I tested my changes with PTX, and they seem to work fine, so, we'd likely not require additional formats. |
| // REQUIRES: zstd, opencl-aot, cpu, linux | ||
|
|
||
| ////////////////////// Compile device images | ||
| // RUN: %clangxx -fsycl -fsycl-targets=spir64_x86_64 -fsycl-host-compiler=clang++ -fsycl-host-compiler-options='-std=c++17 -Wno-attributes -Wno-deprecated-declarations -fPIC -DENABLE_KERNEL1' -DENABLE_KERNEL1 -c %s -o %t_kernel1_aot.o |
There was a problem hiding this comment.
Unless you specifically wanted to test compilation with a 3rd-party host compiler you don't need -fsycl-host-compiler and -fsycl-host-compiler-options flags
There was a problem hiding this comment.
I wanted to have a test that mimics the compilation toolchain that PyTorch team use (as described here: https://github.com/intel/torch-xpu-ops/blob/main/cmake/BuildFlags.cmake#L63). They use gcc for final linkage. The problem with using gcc here in E2E test is that we'd have to explicitly provide path to sycl headers and library (See the older version of this test: https://github.com/intel/llvm/blob/1d8181335fb188aa4ae0ad39b3826a4162b200d2/sycl/test-e2e/Compression/compression_seperate_compile.cpp). AFAIK, we don't have LIT substitutions to get path to SYCL headers and library, and so, I ended up using clang++ as "3rd party" compiler, with which I can just use -fsycl to get the include directory and SYCL library.
There was a problem hiding this comment.
I wanted to have a test that mimics the compilation toolchain that PyTorch team use
Then I think it worth noting that in a comment within the test, or otherwise it seems like an unnecessary overcomplication
| if sp[0] == 0: | ||
| config.available_features.add("preview-breaking-changes-supported") | ||
|
|
||
| # Check if clang is built with ZSTD and compression support. |
There was a problem hiding this comment.
There is a way simpler way. Use lit.site.cfg.py.in to propagate a value of CMake variable into this python script.
I would also explore how LLVM propagates that. There are tests in LLVM which require zstd feature, so I wonder if we can call some LIT helper to get this feature automatically propagated into LIT for us
There was a problem hiding this comment.
As discussed offline, passing LLVM_ENABLE_ZSTD from CMake to LIT won't work here because E2E tests can be built standalone, like what we do in CI.
LLVM seems to pass CMake Variables to LIT: https://github.com/llvm/llvm-project/blob/main/llvm/test/lit.site.cfg.py.in#L37
There was a problem hiding this comment.
Yeah, good point. I still wonder if there is a simpler way (i.e. some existing helper for running an executable and getting its output, but if no, then we will have to leave with what we have.
BTW, I'm sure that compiler is able to read the program from stdin, so you can maybe save on file operations here
|
@bso-intel @intel/llvm-reviewers-runtime ping! |
| llvm::compression::zstd::compress( | ||
| ArrayRef<unsigned char>( | ||
| (const unsigned char *)(Bin->getBufferStart()), | ||
| Bin->getBufferSize()), | ||
| CompressedBuffer, OffloadCompressLevel); |
There was a problem hiding this comment.
When the crash occurs when compression failed, the error message that the SYCL end-user will receive may not be useful.
For example, "Failed to create ZSTD_CCtx", ""Failed to set ZSTD_c_compressionLevel", etc.
It would be much better user experience if they get a message like "Device image compression failed." + e.what().
| "'--offload-compress' option is specified but zstd " | ||
| "is not available. The device image will not be " | ||
| "compressed."); |
There was a problem hiding this comment.
This kind of error message is good since the SYCL end-user can understand what went wrong.
In 946a738, I've wrapped zstd::compress in try/catch to throw a more meaningful error message. Note that this will only work if DPC++ is built with |
|
@intel/llvm-gatekeepers The PR is ready to be merged. All the downstream infrastructure, along with intel/llvm CI machines, is ready with zstd installed. |
|
@uditagarwal97 Could you please take a look at post-commit failures: https://github.com/intel/llvm/actions/runs/11468699849/job/31915329901 Failed Tests (2): On AMD/HIP |
| "-DLLVM_ENABLE_PROJECTS={}".format(llvm_enable_projects), | ||
| "-DSYCL_BUILD_PI_HIP_PLATFORM={}".format(sycl_build_pi_hip_platform), | ||
| "-DLLVM_BUILD_TOOLS=ON", | ||
| "-DLLVM_ENABLE_ZSTD=ON", |
There was a problem hiding this comment.
I think we shouldn't turn on these by default? We should just turn on them in if args.ci_defaults:
There was a problem hiding this comment.
The idea behind turning them on by default is to build the compiler with device image compression support if the user has zstd-dev package installed. If zstd is not found, there shouldn't be any build error.
There was a problem hiding this comment.
there are configurate failures.
There was a problem hiding this comment.
CMake Error at lib/Support/CMakeLists.txt:327 (get_property):
get_property could not find TARGET zstd::libzstd_static. Perhaps it has
not yet been created.
CMake Error at lib/Support/CMakeLists.txt:330 (get_property):
get_property could not find TARGET zstd::libzstd_static. Perhaps it has
not yet been created.
There was a problem hiding this comment.
yeah local build is cooked for me too, we need to revert the on by zstd default part at least
There was a problem hiding this comment.
PR to temporarily turn off zstd by default: #15833
PR to disable the failing tests on HIP: #15830 |

This PR adds support for device image compression for the old offloading model. I'll make another follow-up PR to extend support for the new offload model.
Design summary:
This PR introduces ZSTD (https://github.com/facebook/zstd) as a 3rd party dependency of DPCPP. Similar to upstream LLVM, we expect user to have
zstd-devpackage installed on their machine - we won't be installing zstd from sources.How to use
To compress device images, add
--offload-compressCLI option to your clang invocation. Note that we compress device images only if the size of device images exceeds a threshold, which is 512 bytes by default. Moreover, by default, we use ZSTD level 10 for compression. ZSTD compression levels provides a tradeoff between (de)compression time and compression ratio, and the compression level can be changed using--offload-compression-level=<int>CLI option.