aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Transforms/Utils/SimplifyIndVar.cpp
diff options
context:
space:
mode:
authorMichał Górny <mgorny@moritz.systems>2020-11-04 10:16:30 +0100
committerMichał Górny <mgorny@moritz.systems>2020-11-05 17:49:46 +0100
commit2c2eb5e6702bf3bbb8fb8f09790b1ab7b139e879 (patch)
treeee0dad71b2fe2a587e42cee9c46bb2a1060aa8dc /llvm/lib/Transforms/Utils/SimplifyIndVar.cpp
parent6ba2c2bf90f23381c1d052acb010cee364bebe8e (diff)
downloadllvm-2c2eb5e6702bf3bbb8fb8f09790b1ab7b139e879.zip
llvm-2c2eb5e6702bf3bbb8fb8f09790b1ab7b139e879.tar.gz
llvm-2c2eb5e6702bf3bbb8fb8f09790b1ab7b139e879.tar.bz2
[lldb] Enable FreeBSDRemote plugin by default and update test status
The new FreeBSDRemote plugin has reached feature parity on i386 and amd64 targets. Use it by default on these architectures, while allowing the use of the legacy plugin via FREEBSD_LEGACY_PLUGIN envvar. Revisit the method of switching plugins. Apparently, the return value of PlatformFreeBSD::CanDebugProcess() is what really decides whether the legacy or the new plugin is used. Update the test status. Reenable the tests that were previously disabled on FreeBSD and do not cause hangs or are irrelevant to FreeBSD. Mark all tests that fail reliably as expectedFailure. For now, tests that are flaky (i.e. produce unstable results) are left enabled and cause unpredictable test failures. Differential Revision: https://reviews.llvm.org/D90757
Diffstat (limited to 'llvm/lib/Transforms/Utils/SimplifyIndVar.cpp')
0 files changed, 0 insertions, 0 deletions