aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Transforms/Utils/LoopUtils.cpp
diff options
context:
space:
mode:
authorPavel Labath <pavel@labath.sk>2020-10-09 11:23:17 +0200
committerPavel Labath <pavel@labath.sk>2020-10-12 13:46:17 +0200
commite2f1fe361a9c7616a1d6459b036d15f47da4a073 (patch)
treec692c3ce81370af66faccddf07e2f52014e495b5 /llvm/lib/Transforms/Utils/LoopUtils.cpp
parent8f1de22c7681a21fcdbe2d8c39de7698baab724a (diff)
downloadllvm-e2f1fe361a9c7616a1d6459b036d15f47da4a073.zip
llvm-e2f1fe361a9c7616a1d6459b036d15f47da4a073.tar.gz
llvm-e2f1fe361a9c7616a1d6459b036d15f47da4a073.tar.bz2
[lldb/Utility] Introduce UnimplementedError
This is essentially a replacement for the PacketUnimplementedError previously present in the gdb-remote server code. The reason I am introducing a generic error is because I wanted the native process classes to be able to signal that they do not support some functionality. They could not use PacketUnimplementedError as they are independent of a specific transport protocol. Putting the error class in the the native process code was also not ideal because the gdb-remote code is also used for lldb-server's platform mode, which does not (should not) know how to debug individual processes. I'm putting it under Utility, as I think it can be generally useful for notifying about unsupported/unimplemented functionality (and in particular, for programatically testing whether something is unsupported). Differential Revision: https://reviews.llvm.org/D89121
Diffstat (limited to 'llvm/lib/Transforms/Utils/LoopUtils.cpp')
0 files changed, 0 insertions, 0 deletions