-
Notifications
You must be signed in to change notification settings - Fork 787
[SYCL] Deny pragma spelling for SYCL-specific attributes #1815
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
TBH, I think we can also remove 'pragma spelling' for |
I don't have a strong opinion, but I don't know how heavy the pragma spelling for thoseis used for OpenCL. Do we know? |
Except of loop pragmas (unroll, ivdep etc), I have never encountered any pragmas in OpenCL. |
Then I think we can remove the pragma spelling for IntelReqdGroupSize, and if there's a regression revert that part. Whats the logic for wanting to leave |
It's not Intel-specific attribute coming from OpenCL core spec itself.
So it might be safe to remove the spelling for it as well. |
@keryell may be you know if any of your customers use 'pragma' spelling? |
Signed-off-by: Dmitry Sidorov <[email protected]>
Signed-off-by: Dmitry Sidorov <[email protected]>
4683ee5
to
4fe536e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm happy with this. @keryell stop this if you think its necessary, otherwise I think we can just wait to see if it breaks anything.
@@ -136,14 +135,10 @@ | |||
// CHECK-NEXT: Pointer (SubjectMatchRule_record_not_is_union) | |||
// CHECK-NEXT: ReleaseHandle (SubjectMatchRule_variable_is_parameter) | |||
// CHECK-NEXT: RenderScriptKernel (SubjectMatchRule_function) | |||
// CHECK-NEXT: ReqdWorkGroupSize (SubjectMatchRule_function) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have OpenCL background, so I cannot say is correct this change or not, but this particular attribute ReqdWorkGroupSize
is OpenCL specific and it is added not by us.
Suggest you go through community with change for this attribute first.
I think you will get answers on your questions regarding this attribute.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, lets stick with leaving reqd_work_group_size attribute alone.
Traditional Xilinx tools use a lot of While I am an advocate of no user-visible |
Signed-off-by: Dmitry Sidorov <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the discussion guys, I think we've bottomed out, so I'm approving.
Signed-off-by: Dmitry Sidorov [email protected]