Skip to content

Conversation

mdtoguchi
Copy link
Contributor

Add a basic E2E test that exercises early-AOT behavior when using -fsycl -fno-sycl-rdc -c -fsycl-targets=spir64_gen when building objects.

Add a basic E2E test that exercises early-AOT behavior when using -fsycl
-fno-sycl-rdc -c -fsycl-targets=spir64_gen when building objects.
@mdtoguchi mdtoguchi temporarily deployed to WindowsCILock October 28, 2023 00:20 — with GitHub Actions Inactive
@mdtoguchi mdtoguchi temporarily deployed to WindowsCILock October 28, 2023 00:34 — with GitHub Actions Inactive
@mdtoguchi mdtoguchi temporarily deployed to WindowsCILock October 28, 2023 20:05 — with GitHub Actions Inactive
@mdtoguchi mdtoguchi temporarily deployed to WindowsCILock October 28, 2023 20:17 — with GitHub Actions Inactive
@mdtoguchi mdtoguchi marked this pull request as ready for review October 28, 2023 23:13
@mdtoguchi mdtoguchi requested a review from a team as a code owner October 28, 2023 23:13
Copy link
Contributor

@maksimsab maksimsab left a comment

Choose a reason for hiding this comment

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

LGTM.

Btw, what is the difference between early-AOT and just AOT ?

@againull againull merged commit 4cf7087 into intel:sycl Oct 30, 2023
@mdtoguchi
Copy link
Contributor Author

LGTM.

Btw, what is the difference between early-AOT and just AOT ?

early-AOT allows a user to create a fully linked device binary when generating the object. Consumers of this object will have the full device binary unbundled and linked directly into their final executable without having the requirement of the AOT offline compiler and the additional steps associated. AOT compilation typically occurs during link time.

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