tree 683d5b52b867e2dc0b538059223061e619a660f2
parent c1808464b75435da9dcbb703e2fcf9d20cbb36ec
author Johannes Doerfert <johannes@jdoerfert.de> 1613327156 -0600
committer Copybara-Service <copybara-worker@google.com> 1613736169 -0800

[OpenMP][FIX] Avoid use of stack allocations in asynchronous calls

As reported by Guilherme Valarini [0], we used to pass stack allocations
to calls that can nowadays be asynchronous. This is arguably a problem
and it will inevitably result in UB. To remedy the situation we
allocate the locations as part of the AsyncInfoTy object. The lifetime
of that object matches what we need for now. If the synchronization is
not tied to the AsyncInfoTy object anymore we might need to have a
different buffer construct in global space.

This should be back-ported to LLVM 12 but needs slight modifications as
it is based on refactoring patches we do not need to backport.

[0] https://lists.llvm.org/pipermail/openmp-dev/2021-February/003867.html

Reviewed By: JonChesterfield

Differential Revision: https://reviews.llvm.org/D96667

GitOrigin-RevId: 2518cc65d2a7564bb49d7b806f23dd47212dcefd