-
Notifications
You must be signed in to change notification settings - Fork 8
Add private variables to openMP loops #88
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
Closed
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
a52ba02
Add ability to declare privat variables in an openmp loop.
mns-nordicals 7c80695
double-pop bug for nested OpenMP loops by adding an abort flag so the…
mns-nordicals ad84514
remove race condition checks as it might be a bit too difficult
mns-nordicals a4b381e
Allow sappy to also use private variables
mns-nordicals 4f72349
Revert "Allow sappy to also use private variables"
mns-nordicals 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
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
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.
When a private variable is shadowed in a closure scope, its Fortran symbol can be renamed via
make_shadow_fortran_name(e.g.,i__local_). Here the private list is built withfortranize_name, which ignores those scope-specific renames and emits the base name instead. In nested closures or when a variable name collides with a parent scope, this produces!$omp parallel do private(i)even though the actual loop variable isi__local_, leading to a compile error (“symbol not declared”) or leaving the true variable non-private. Consider deriving private names from the scope (e.g.,scope_fortran_symbolorget0(name, scope)@name) rather than re-fortranizing the raw symbol.Useful? React with 👍 / 👎.