diff options
| author | Kareem Ergawy <kareem.ergawy@amd.com> | 2025-01-16 19:10:12 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-01-16 19:10:12 +0100 |
| commit | a0406ce823e8f1c1993b565d08b045c0104c3a5a (patch) | |
| tree | ccffdd06935c1a1f20e96a66cc9c2c37010131f7 /lldb/source/Plugins/ScriptInterpreter/Python/SWIGPythonBridge.h | |
| parent | 6b3ba6677d64e394b9c929ea0d1f7c54e3146fda (diff) | |
| download | llvm-a0406ce823e8f1c1993b565d08b045c0104c3a5a.zip llvm-a0406ce823e8f1c1993b565d08b045c0104c3a5a.tar.gz llvm-a0406ce823e8f1c1993b565d08b045c0104c3a5a.tar.bz2 | |
[flang][OpenMP] Add `hostIsSource` paramemter to `copyHostAssociateVar` (#123162)
This fixes a bug when the same variable is used in `firstprivate` and
`lastprivate` clauses on the same construct. The issue boils down to the
fact that `copyHostAssociateVar` was deciding the direction of the copy
assignment (i.e. the `lhs` and `rhs`) based on whether the
`copyAssignIP`
parameter is set. This is not the best way to do it since it is not
related to whether we doing a copy from host to localized copy or the
other way around. When we set the insertion for `firstprivate` in
delayed privatization, this resulted in switching the direction of the
copy assignment. Instead, this PR adds a new paramter to explicitely
tell
the function the direction of the assignment.
This is a follow up PR for
https://github.com/llvm/llvm-project/pull/122471, only the latest commit
is relevant.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/SWIGPythonBridge.h')
0 files changed, 0 insertions, 0 deletions