Workaround for the CCE 17 requiring explicit copy for reduction variables
What is the bug
CCE 17 needed for AMD GPUs on LUMI now requires an explicit copy of reduction variables.
How do you fix it
Add copy clauses for the reduction variables.
How urgent is the bugfix
-
I need it as soon as possible -
I can wait for a couple of days -
None of my current codes is directly affected
Mandatory steps before review
-
Gitlab CI passes (Hint: use make format
for linting) -
Bugfix is covered by additional unit tests -
Mark the merge request as ready by removing Draft:
Mandatory steps before merge
-
Test coverage does not decrease -
Reviewed by a maintainer -
Incorporate review suggestions -
Prior to merging, please remove any boilerplate from the MR description, retaining only the What is the bug and How do you fix it section to maintain -
Remember to edit the commit message and select the proper changelog category (feature/bugfix/other)
You are not supposed to merge this request by yourself, the maintainers of fortan-support take care of this action!
Edited by Yen-Chen Chen
Merge request reports
Activity
assigned to @k202137
added 10 commits
-
e781b0e5...35723fc9 - 8 commits from branch
master
- b963a189 - Workaround for the CCE 17 requiring explicit copy for reduction variables
- 20854d0b - Applied ACC style patch
-
e781b0e5...35723fc9 - 8 commits from branch
mentioned in commit 986e3290
mentioned in commit 0fa27b5c
Please register or sign in to reply