Skip to content

[SYCL][ABI-break] Promote extended CG/handler members #6555

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

Merged
merged 5 commits into from
Aug 17, 2022

Conversation

sergey-semenov
Copy link
Contributor

Several new members were added to CG/handler via the extended member
workaround. This patch promotes them to actual fields of those classes
now that the ABI can be broken.

Several new members were added to CG/handler via the extended member
workaround. This patch promotes them to actual fields of those classes
now that the ABI can be broken.
@sergey-semenov sergey-semenov requested a review from a team as a code owner August 10, 2022 17:05
@sergey-semenov
Copy link
Contributor Author

sergey-semenov commented Aug 10, 2022

I'm planning to remove the extended member mechanism in a separate follow-up PR, just so it would be easier to recover it if we need to add new members to CG classes in the future.

@sergey-semenov
Copy link
Contributor Author

@smaslov-intel Could you please review?

@@ -30,7 +30,7 @@ set(SYCL_MINOR_VERSION 7)
set(SYCL_PATCH_VERSION 0)
# Don't forget to re-enable sycl_symbols_windows.dump once we leave ABI-breaking
# window!
set(SYCL_DEV_ABI_VERSION 8)
set(SYCL_DEV_ABI_VERSION 9)
Copy link
Contributor

Choose a reason for hiding this comment

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

I think I saw this change already in another ABI breaking change today, so someone will get a conflict.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, that goes for all ABI break PRs with the way we handle incrementing SYCL_DEV_ABI_VERSION right now.

Copy link
Contributor

@smaslov-intel smaslov-intel left a comment

Choose a reason for hiding this comment

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

LGTM

@sergey-semenov
Copy link
Contributor Author

@steffenlarsen Could you please merge this one?

@steffenlarsen steffenlarsen merged commit 54655a2 into intel:sycl Aug 17, 2022
@sergey-semenov
Copy link
Contributor Author

Looks like this introduced a post-commit failure, looking into it

sergey-semenov added a commit to sergey-semenov/llvm that referenced this pull request Aug 17, 2022
steffenlarsen pushed a commit that referenced this pull request Aug 18, 2022
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