-
Notifications
You must be signed in to change notification settings - Fork 787
[SYCL][FPGA] Fix the way we handle duplicate vs conflicting values with loop attributes #14342
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
Conversation
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
…LIntelRegister, SYCLIntelMemory) This patch uses MutualExclusions tablegen support to allow us to remove a custom diagnostic checking codes with FPGA attributes: [[intel:fpga_register]] and [[intel::fpga_memory]]. No test is added as we alreday have an existing LIT test (SemaSYCL/local.cpp) that shows the behavior.
…es with loop attributes This patch improves diagnostic supports by resolving bugs the way we handle duplicate vs conflicting values with the following SYCL FPGA loop attributes: [[intel::max_reinvocation_delay()]] [[intel::initiation_interval()]] [[intel::max_concurrency()]] [[intel::speculated_iterations()]] [[intel::max_interleaving()]] The patch addresses issues in the test case below, which previously missed diagnostics due to a discontinuation in the while loop while checking for duplicate versus conflicting attribute values in the routine CheckForDuplicateAttrs(). Example with `speculated_iterations` attribute: Before the fix: [[intel::speculated_iterations(1)]] // expected-note {{previous attribute is here}} [[intel::speculated_iterations(1)]] // OK [[intel::speculated_iterations(2)]] // expected-error {{conflicting loop attribute 'speculated_iterations'}} [[intel::speculated_iterations(4)]] // OK for (int i = 0; i != 10; ++i) { a[i] = 0; } After the fix: [[intel::speculated_iterations(1)]] // expected-note 2 {{previous attribute is here}} [[intel::speculated_iterations(1)]] // OK [[intel::speculated_iterations(2)]] // expected-error {{conflicting loop attribute 'speculated_iterations'}} [[intel::speculated_iterations(4)]] // expected-error {{conflicting loop attribute 'speculated_iterations'}} for (int i = 0; i != 10; ++i) { a[i] = 0; } Signed-off-by: Soumi Manna <[email protected]>
premanandrao
approved these changes
Jun 28, 2024
Thank you @premanandrao for reviews! |
@intel/llvm-gatekeepers, this PR is ready to merge. Thank you |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This patch improves diagnostic supports by resolving bugs the way we handle duplicate vs conflicting values with the following SYCL FPGA loop attributes:
The patch addresses issues in the test case below, which previously missed diagnostics due to a discontinuation in the while loop while checking for duplicate versus conflicting attribute values in the routine CheckForDuplicateAttrs().
Example with `speculated_iterations' attribute:
Signed-off-by: Soumi Manna [email protected]