summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Transforms/Utils/LoopUnrollPeel.cpp
diff options
context:
space:
mode:
authorJonas Devlieghere <jonas@devlieghere.com>2019-05-08 16:31:47 +0000
committerJonas Devlieghere <jonas@devlieghere.com>2019-05-08 16:31:47 +0000
commit9f15718b3dd405adb2477a121e1030a0e81d00fd (patch)
tree00b3ce9b44ec075f9f788d048fae86ca7425493e /llvm/lib/Transforms/Utils/LoopUnrollPeel.cpp
parente461e9a77d24cbd7eb0c9ce331eeb4d69a5b186c (diff)
downloadbcm5719-llvm-9f15718b3dd405adb2477a121e1030a0e81d00fd.tar.gz
bcm5719-llvm-9f15718b3dd405adb2477a121e1030a0e81d00fd.zip
[Docs] list command: lldb run <args>
The run command is only an abbreviation for the more verbose process launch -- <args> but it works just as with GDB and therefore should be mentioned in the GDB to LLDB command map. For educational purposes I've not listed it as the first option on the LLDB side so that new LLDB user can, if they want, also know what the "native" way is for LLDB. Here's the help documentation for the run command in lldb which gives proof: > (lldb) help run > Launch the executable in the debugger. > > Syntax: run [<run-args>] > > Command Options Usage: > run [<run-args>] > > 'run' is an abbreviation for 'process launch -c /bin/sh --' Patch by: Konrad Kleine Differential revision: https://reviews.llvm.org/D61483 llvm-svn: 360269
Diffstat (limited to 'llvm/lib/Transforms/Utils/LoopUnrollPeel.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud