================
@@ -219,6 +430,33 @@ class OMPMapInfoFinalizationPass
mapClauseOwner.getMapOperandsMutable().assign(newMapOps);
----------------
agozillon wrote:
It shouldn't (at least if I am understanding your comment correctly), I believe
this little snippet misses the preceding block of code which builds up the
newMapOps from the prior contained map operations and inserts the new ones in
position before re-assignment. The omp-map-info-finalization.fir test should
hopefully show that no prior map operations are dropped, if not, happy to add a
test which you think will cover the case/verify it does indeed work! :-)
https://github.com/llvm/llvm-project/pull/96266
_______________________________________________
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
