Skip to content

Conversation

@LU-JOHN
Copy link
Contributor

@LU-JOHN LU-JOHN commented Jun 27, 2024

Describe behavior of sycl-post-link in support of dynamic linking

Signed-off-by: Lu, John <john.lu@intel.com>
@LU-JOHN LU-JOHN requested a review from a team as a code owner June 27, 2024 21:40
@LU-JOHN
Copy link
Contributor Author

LU-JOHN commented Jun 27, 2024

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>
@KseniyaTikhomirova
Copy link
Contributor

@AlexeySachkov and @asudarsa kindly ping. I will approve after.

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Thus, when supporting dynamic linking a dependency to a canBeImportedFunction will not
Thus, when supporting dynamic linking a dependency to a `canBeImportedFunction` will not

Copy link
Contributor

@asudarsa asudarsa Jul 3, 2024

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>
@AlexeySachkov AlexeySachkov merged commit 1f2ea6d into intel:sycl Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants