Skip to content

Fix llorg/sycl-web pulldown issue #5448

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

Closed
wants to merge 4 commits into from

Conversation

zahiraam
Copy link
Contributor

@zahiraam zahiraam commented Feb 1, 2022

Signed-off-by: Zahira Ammarguellat zahira.ammarguellat@intel.com

Signed-off-by: Zahira Ammarguellat <zahira.ammarguellat@intel.com>
Signed-off-by: Zahira Ammarguellat <zahira.ammarguellat@intel.com>
Signed-off-by: Zahira Ammarguellat <zahira.ammarguellat@intel.com>
Signed-off-by: Zahira Ammarguellat <zahira.ammarguellat@intel.com>
@zahiraam zahiraam marked this pull request as ready for review February 2, 2022 13:05
@zahiraam zahiraam requested review from a team as code owners February 2, 2022 13:05
@smanna12
Copy link
Contributor

smanna12 commented Feb 2, 2022

Could you please add a test? Thanks

@@ -1139,6 +1139,9 @@ class CXXRecordDecl : public RecordDecl {
/// \note This does NOT include a check for union-ness.
bool isEmpty() const { return data().Empty; }

void setInitMethod(bool Val) { data().HasInitMethod = Val; }
Copy link
Contributor

@smanna12 smanna12 Feb 2, 2022

Choose a reason for hiding this comment

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

@Fznamznon
Copy link
Contributor

Shouldn't the fix be included into #5427 . @vmaksimo WDYT?

@zahiraam
Copy link
Contributor Author

zahiraam commented Feb 2, 2022

Shouldn't the fix be included into #5427 . @vmaksimo WDYT?

I think it should. But I am wondering if better yet, the changes to SemaDecl.cpp shouldn't be up-streamed? And only make the change here for accessor.hpp?

Shouldn't the fix be included into #5427 . @vmaksimo WDYT?

@Fznamznon
Copy link
Contributor

I am wondering if better yet, the changes to SemaDecl.cpp shouldn't be up-streamed?

I'm sure that the check on NewFD->getIdentifier() should be upstreamed. About the check on SYCLIsDevice I'm not that sure, since the attribute doc doesn't say that it shouldn't be used only for device compilation. It is our headers for some reason put some __init methods under SYCL_DEVICE_ONLY macro.
Probably it makes sense to commit the fix together with pulldown as well to unblock pulldown.

@zahiraam
Copy link
Contributor Author

zahiraam commented Feb 2, 2022

I am wondering if better yet, the changes to SemaDecl.cpp shouldn't be up-streamed?

I'm sure that the check on NewFD->getIdentifier() should be upstreamed. About the check on SYCLIsDevice I'm not that sure, since the attribute doc doesn't say that it shouldn't be used only for device compilation. It is our headers for some reason put some __init methods under SYCL_DEVICE_ONLY macro. Probably it makes sense to commit the fix together with pulldown as well to unblock pulldown.

I will make the change for NewFD->getIdentifier() in llorg and ask you to review it. To minimize the next pulldown "headaches" :)

@zahiraam
Copy link
Contributor Author

zahiraam commented Feb 2, 2022

I am wondering if better yet, the changes to SemaDecl.cpp shouldn't be up-streamed?

I'm sure that the check on NewFD->getIdentifier() should be upstreamed. About the check on SYCLIsDevice I'm not that sure, since the attribute doc doesn't say that it shouldn't be used only for device compilation. It is our headers for some reason put some __init methods under SYCL_DEVICE_ONLY macro. Probably it makes sense to commit the fix together with pulldown as well to unblock pulldown.

I will make the change for NewFD->getIdentifier() in llorg and ask you to review it. To minimize the next pulldown "headaches" :)

And the rest of the changes can just be committed here. Thanks.

@vmaksimo
Copy link
Contributor

vmaksimo commented Feb 2, 2022

I see it's the best solution - to commit the fix as a part of #5427 and to upstream the needed fix to llorg to minimize next week's pulldown problems. Thanks!

@zahiraam zahiraam closed this Feb 7, 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.

4 participants