-
Notifications
You must be signed in to change notification settings - Fork 796
[clang][SYCL] Allow structs as free function kernel arguments #15334
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
martygrant
merged 19 commits into
intel:sycl
from
Fznamznon:free-functions-struct-params
Sep 26, 2024
Merged
Changes from 16 commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
80491c3
[clang][SYCL] Allow structs as free function kernel arguments
Fznamznon 3fbb50c
Add AST test
Fznamznon 3e5332e
Add test for integration header generation, extend e2e test
Fznamznon c8bf832
Maybe fix test on win
Fznamznon 95cfe15
Clean up SemaSYCL
Fznamznon 6d8a28f
Diagnose bad struct kernel parameters
Fznamznon 7b17d82
Fix format
Fznamznon efcfc47
Remove obsolete TODO
Fznamznon 4e293da
Add codegen test to see address spaces
Fznamznon 34524f4
Incorportate review feedback
Fznamznon dd52ed5
Cleanup
Fznamznon f9a1641
Merge branch 'sycl' into free-functions-struct-params
Fznamznon ef3ca91
Diagnose special types in structs since they are not yet supported.
Fznamznon 431a405
Rename createStructTemporary -> createCopyInitExpr
Fznamznon 0b88367
Improve diagnotic messages
Fznamznon ce98062
Create isForwardDeclarable
Fznamznon 9885f5a
Merge branch 'sycl' into free-functions-struct-params
Fznamznon 2eb3d61
Resolve diagnostic concerns
Fznamznon 9622e3e
Merge branch 'sycl' into free-functions-struct-params
Fznamznon File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Uh oh!
There was an error while loading. Please reload this page.
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 think having different diagnostics for free function parameter type and kernel param type is unnecessary. Other than the diagnostics you added/modified in this PR, won't other invalid types in free functions generate the old diagnostic
err_bad_kernel_param_type? IMO I think we can keep the old diagnostic, passing type to it. The note diagnostic can be generated additionally for extra information where requiredThere 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 agree the diagnostics could be unified, but that would require changes to the existing diagnostics since their message text explicitly references the concept of a "kernel name". I'm not sure such unification would provide much benefit.
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 used
err_bad_kernel_param_typeinstead of a new one.@tahonermann , I think @elizabethandrews meant another set of diagnostics.