-
Notifications
You must be signed in to change notification settings - Fork 15.3k
[Flang] - Enhance testing for strictly-nested teams in target regions. #168437
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
bhandarkar-pranav
merged 3 commits into
llvm:main
from
bhandarkar-pranav:flang/fix_153173
Nov 25, 2025
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| ! RUN: %python %S/../test_errors.py %s %flang_fc1 -fopenmp | ||
|
|
||
| program main | ||
| implicit none | ||
| integer, parameter :: n = 100 | ||
| integer, parameter :: expected = n+2 | ||
| integer :: i | ||
| integer :: counter | ||
|
|
||
| counter = 0 | ||
| !ERROR: TARGET construct with nested TEAMS region contains statements or directives outside of the TEAMS construct | ||
| !$omp target map(tofrom:counter) | ||
| counter = counter+1 | ||
| !$omp teams distribute reduction(+:counter) | ||
| do i=1, n | ||
| counter = counter+1 | ||
| end do | ||
| counter = counter+1 | ||
| !$omp end target | ||
| end program |
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.
Not exactly relevant to this PR since a similar check is used somewhere else. But for the following example:
Would the semantic check trigger in this case? I think it won't since
GetDirectiveNest(TargetBlockOnlyTeams)will return a non-zero result.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 coudn't nest a
targetdirective inside theteamsdirective because that is not allowed, but I did the followingThis compiled fine but it shouldn't have for the reason you mentioned. Strangely enough,
gfortranalso accepts the code above, only warning about reverse-offloading. I am torn between spending time fixing it on the one hand while on the other hand letting what seems to be an obscure case slide.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.
No need to fix it, at least in this PR. Specially since the test is used somewhere else. The way the directive-nest test is currently implemented is just surprising to me (seems a bit too permisive) and wanted to verify if this is really the case.