-
Notifications
You must be signed in to change notification settings - Fork 790
[Clang][Driver] Disable ITT annotations in device code by default #14910
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
@uditagarwal97, can you expand on that? My understanding that external tools like Intel Inspector rely on these annotations. Did you coordinate this change with oneAPI tools teams? |
Note, the ITT annotation functions are currently marked optnone and hence require the the SPIR-V OptNone function control bit, which not all SPIR-V consumers support. This means that disabling the ITT annotations by default will also result in more portable SPIR-V modules by default. I agree with this change making the ITT annotations opt-in (for users that want this functionality), rather than opt-out. |
This reverts commit 91d1483.
Removed this change from -fpreview-breaking-changes after internal discussion |
Looks good from VTune POV. ITT generally does not work for XPU kernels and even if the target device is CPU the execution is done through OpenCL so it would not have worked anyway. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some comments on test updates - nothing blocking.
Fixed in 65a6a64 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks - LGTM
@intel/llvm-gatekeepers the PR is ready to be merged. |
ITT annotations bloats the device code while offering limited benefit to the end user. That's why, this PR disables ITT annotations by default.
After this change, to enable ITT annotations, we would have to use
-fsycl-instrument-device-code
CLI option.