Skip to content

[sycl-post-link] Do not treat declarations as entry points #4927

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

AlexeySachkov
Copy link
Contributor

If declaration is treated as entry point, then we will create a
device image which claims that it contains particular kernel,
while it actually doesn't - that leads to errors at runtime.

Kernel declarations can appear in input modules as a side
effect of #4409. The PR postponed removal of
@llvm.used variable from input modules, which results
in kernel declarations left in modules after split between
SYCL and ESIMD kernels.

If declaration is treated as entry point, then we will create a
device image which claims that it contains particular kernel,
while it actually doesn't - that leads to errors at runtime.

Kernel declarations can appear in input modules as a side
effect of intel#4409. The PR postponed removal of
`@llvm.used` variable from input modules, which results
in kernel declarations left in modules after split between
SYCL and ESIMD kernels.
@AlexeySachkov
Copy link
Contributor Author

@mlychkov, @kbobrovs, friendly ping

@dm-vodopyanov dm-vodopyanov merged commit 2809005 into intel:sycl Nov 12, 2021
@AlexeySachkov AlexeySachkov deleted the private/asachkov/ignore-declarations-in-device-code-split branch May 22, 2024 09:50
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.

3 participants