-
Notifications
You must be signed in to change notification settings - Fork 788
[SYCL][libdevice] Add -fsycl-device-lib-online-link option. #6167
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
When this option is used, we use online link for SYCL device libraries, otherwise, we use offline link, all wrapper and fallback device libraries are linked with user's device image in compilation time. Signed-off-by: jinge90 <[email protected]>
Signed-off-by: jinge90 <[email protected]>
Signed-off-by: jinge90 <[email protected]>
Signed-off-by: jinge90 <[email protected]>
@jinge90, can you please add update of https://github.com/intel/llvm/blob/sycl/sycl/doc/UsersManual.md into this patch? |
…or the option Signed-off-by: jinge90 <[email protected]>
Doc added. |
Co-authored-by: Pavel Chupin <[email protected]>
Hi, @mdtoguchi Thanks very much. |
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.
LGTM, thanks!
Currently, sycl-post-link tool will analyze user's device image and record which device libraries are actually required by user, sycl runtime will read the info and load the required fallback spv file. However, old compiler would always mark "cassert" fallback spv as required, this was to bypass a FE issue. So, if anyone uses old compiler + new SYCL runtime with online link enabled, unnecessary cassert fallback spv loading will be observed. This PR will ignore "cassert" fallback spv in sycl runtime, ignoring it is OK for now since "cassert" fallback has not been fully implemented. This PR depends on #6167 Signed-off-by: jinge90 <[email protected]>
When this option is used, we use online link for SYCL device libraries,
otherwise, we use offline link, all wrapper and fallback device libraries
are linked with user's device image in compilation time.
Signed-off-by: jinge90 [email protected]