aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/MC/MCObjectFileInfo.cpp
diff options
context:
space:
mode:
authorJohannes Doerfert <johannes@jdoerfert.de>2021-02-14 12:25:56 -0600
committerJohannes Doerfert <johannes@jdoerfert.de>2021-02-16 15:38:11 -0600
commit2518cc65d2a7564bb49d7b806f23dd47212dcefd (patch)
treef6bc055aa2b58544adeb227f70f7c658f39a9da2 /llvm/lib/MC/MCObjectFileInfo.cpp
parent758b8499310a5d44a41de67d656bd32dc3fd1023 (diff)
downloadllvm-2518cc65d2a7564bb49d7b806f23dd47212dcefd.zip
llvm-2518cc65d2a7564bb49d7b806f23dd47212dcefd.tar.gz
llvm-2518cc65d2a7564bb49d7b806f23dd47212dcefd.tar.bz2
[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
Diffstat (limited to 'llvm/lib/MC/MCObjectFileInfo.cpp')
0 files changed, 0 insertions, 0 deletions