-
Notifications
You must be signed in to change notification settings - Fork 738
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
[NFC] Describe sycl-post-link support for dynamic linking #14337
Conversation
Signed-off-by: Lu, John <john.lu@intel.com>
Updated text describes current behavior of sycl_post_link. The previous text for sycl_post_link may need more revision. |
Signed-off-by: Lu, John <john.lu@intel.com>
@AlexeySachkov and @asudarsa kindly ping. I will approve after. |
sycl/doc/design/SharedLibraries.md
Outdated
In typical device code splitting, all dependent device code is brought into a split | ||
image in order to construct a complete image. This is impossible with dynamic linking | ||
since the dynamic library may rely on functions that are not defined in the library. | ||
Thus, when supporting dynamic linking a dependency to a canBeImportedFunction will not |
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.
Thus, when supporting dynamic linking a dependency to a canBeImportedFunction will not | |
Thus, when supporting dynamic linking a dependency to a `canBeImportedFunction` will not |
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.
Can we please avoid the use of 'canBeImportedFunction' here. It makes the document a bit unreadable.
Signed-off-by: Lu, John <john.lu@intel.com>
Describe behavior of sycl-post-link in support of dynamic linking