aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/gdbclientutils.py
diff options
context:
space:
mode:
authorJohannes Rudolf Doerfert <doerfert@lassen735.coral.llnl.gov>2022-10-25 22:50:12 -0700
committerJohannes Doerfert <johannes@jdoerfert.de>2022-10-26 10:40:11 -0700
commit41a278f56aab5fa1b4d8e875207771318a8d3ef0 (patch)
tree847f2f32112634745b618648d9333918c7f64f67 /lldb/packages/Python/lldbsuite/test/gdbclientutils.py
parent0af7280a5ee005737fbf1b709909d9600e2b5c75 (diff)
downloadllvm-41a278f56aab5fa1b4d8e875207771318a8d3ef0.zip
llvm-41a278f56aab5fa1b4d8e875207771318a8d3ef0.tar.gz
llvm-41a278f56aab5fa1b4d8e875207771318a8d3ef0.tar.bz2
[OpenMP][FIX] Do not add custom state machine eagerly in LTO runs
If we run LTO optimization we migth end up introducing a custom state machine and later transforming the region into SPMD. This is a problem. While a follow up will introduce a check for the SPMD conversion, this already prevents the eager custom state machine generation. Only if the kernel init function is defined, rather then declared, we will emit a custom state machine. SPMD-zation can happen eagerly though. Tests are adjusted via a weak definition. The LTO test was added to verify this works as expected. Differential Revision: https://reviews.llvm.org/D136740
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/gdbclientutils.py')
0 files changed, 0 insertions, 0 deletions