-
Notifications
You must be signed in to change notification settings - Fork 797
[Driver] Dump device code during SYCL offloading. #11132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@intel/llvm-gatekeepers Hello, this is ready for merge. Waiting for review: WindowsCILock needs approval to start deploying changes. Any tip to get this job running? |
Hi @srividya-sundaram ! Due to CI issues we are currently manually letting windows jobs through. Restarting the jobs only places the runs behind the queue. Additionally, if you don't manually cancel your old processes they may get approved and eat resources, making the wait longer. We apologize for the inconvenience and will get to the runs related to this PR ASAP. |
@intel/llvm-gatekeepers This is ready to merge. |
Thanks @steffenlarsen . I learnt about the Windows CI lock from Stewart offline. |
This PR enables users to dump the device code generated during the SYCL compilation into a user provided directory.
The new option added is : -fsycl-dump-device-code=/path/to/directory/
Example usage:
If somebody runs :
clang++ -fsycl -fsycl-dump-device-code=/path/to/directory test.cpp
the
*.spv
files generated during device compilation show up in/path/to/directory/