aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Transforms/Utils/LoopUtils.cpp
diff options
context:
space:
mode:
authorRaphael Isemann <teemperor@gmail.com>2021-03-29 10:39:10 +0200
committerRaphael Isemann <teemperor@gmail.com>2021-03-29 10:46:14 +0200
commit3c95bdf9fa35f0fe2143ea859b624c8f09513adb (patch)
tree8735d7c790eb568f031b38a2f32be379217f6778 /llvm/lib/Transforms/Utils/LoopUtils.cpp
parent06b03800f3fcbf49f5ddd4145b40f04e4ba4eb42 (diff)
downloadllvm-3c95bdf9fa35f0fe2143ea859b624c8f09513adb.zip
llvm-3c95bdf9fa35f0fe2143ea859b624c8f09513adb.tar.gz
llvm-3c95bdf9fa35f0fe2143ea859b624c8f09513adb.tar.bz2
[lldb] Don't search for system specific strings in assert.test
Commit 6bc1e69de270db8d7191200f54158e4192f997ba changed the search string to also check for the generated strings that surround the plain assert: Assertion `false && "lldb-test assert"' failed ^^^^^^^^^ This causes the test to fail on setups where the generated assert message looks different. E.g., on macOS the generated message looks like this: Assertion failed: (false && "lldb_assert failed"), function lldb_assert This reverts the old behaviour of just checking for the actual string we have inside LLDB.
Diffstat (limited to 'llvm/lib/Transforms/Utils/LoopUtils.cpp')
0 files changed, 0 insertions, 0 deletions