Home
last modified time | relevance | path

Searched refs:LLDB (Results 1 – 25 of 34) sorted by relevance

12

/external/llvm/test/DebugInfo/X86/
Ddebugger-tune.ll4 ; and the apple_names section to distinguish the LLDB case. SCE has neither.
8 …_64-apple-darwin12 -filetype=obj < %s | llvm-readobj -sections - | FileCheck --check-prefix=LLDB %s
14 …filetype=obj -debugger-tune=lldb < %s | llvm-readobj -sections - | FileCheck --check-prefix=LLDB %s
22 ; LLDB-NOT: debug_pubnames
23 ; LLDB: apple_names
24 ; LLDB-NOT: debug_pubnames
/external/swiftshader/third_party/llvm-7.0/llvm/test/DebugInfo/X86/
Ddebugger-tune.ll8 …apple-darwin12 -filetype=obj < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
14 …type=obj -debugger-tune=lldb < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
20 ; LLDB: DW_AT_APPLE_optimized
21 ; LLDB: DW_OP_form_tls_address
Ddebug-loc-frame.ll33 ; LLDB gets the location right without it:
/external/swiftshader/third_party/llvm-7.0/llvm/test/DebugInfo/
Ddwo.ll8 ; The skeleton must come second or LLDB may get confused.
/external/swiftshader/third_party/llvm-7.0/llvm/include/llvm/Target/
DTargetOptions.h95 LLDB, // Tune debug info for lldb. enumerator
/external/llvm/
D.gitignore53 # LLDB, which is tracked independently.
DCODE_OWNERS.TXT35 D: LLDB
/external/llvm/include/llvm/Target/
DTargetOptions.h88 LLDB, // Tune debug info for lldb. enumerator
/external/swiftshader/third_party/llvm-7.0/llvm/
D.gitignore56 # LLDB, which is tracked independently.
DCODE_OWNERS.TXT49 D: LLDB
/external/swiftshader/third_party/llvm-7.0/llvm/docs/
DDebuggingJITedCode.rst31 Apple ships with Xcode has been frozen at 6.3 for a while. LLDB may be a
DLLVMBuild.rst18 on. Related projects in the LLVM system like Clang and LLDB also tend to
31 Clang, and LLDB) is organized into *components*, which define the
DSourceLevelDebugging.rst67 CodeViewDebug. DwarfDebug produces DWARF suitable for use with GDB, LLDB, and
790 These tables are also insufficient for what a debugger like LLDB needs. LLDB
791 uses clang for its expression parsing where LLDB acts as a PCH. LLDB is then
DCodingStandards.rst61 toolchains supported as host compilers. The LLDB project is even more
467 specific, for the same reasons described above. For example, LLDB depends on
468 both clang and LLVM, and clang depends on LLVM. So an LLDB source file should
470 ``llvm`` headers, to reduce the possibility (for example) of an LLDB header
DDeveloperPolicy.rst17 LLDB, libc++, etc.
53 <http://lists.llvm.org/mailman/listinfo/lldb-dev>`_ for LLDB. If you are
/external/llvm/docs/
DDebuggingJITedCode.rst31 Apple ships with Xcode has been frozen at 6.3 for a while. LLDB may be a
DLLVMBuild.rst18 on. Related projects in the LLVM system like Clang and LLDB also tend to
31 Clang, and LLDB) is organized into *components*, which define the
DSourceLevelDebugging.rst67 CodeViewDebug. DwarfDebug produces DWARF sutable for use with GDB, LLDB, and
734 These tables are also insufficient for what a debugger like LLDB needs. LLDB
735 uses clang for its expression parsing where LLDB acts as a PCH. LLDB is then
DDeveloperPolicy.rst17 LLDB, libc++, etc.
53 <http://lists.llvm.org/mailman/listinfo/lldb-dev>`_ for LLDB. If you are
/external/llvm/lib/CodeGen/AsmPrinter/
DDwarfDebug.h302 bool tuneForLLDB() const { return DebuggerTuning == DebuggerKind::LLDB; } in tuneForLLDB()
/external/swiftshader/third_party/llvm-7.0/llvm/lib/CodeGen/AsmPrinter/
DDwarfDebug.h640 bool tuneForLLDB() const { return DebuggerTuning == DebuggerKind::LLDB; } in tuneForLLDB()
DDwarfDebug.cpp309 if (Tuning == DebuggerKind::LLDB) in computeAccelTableKind()
327 DebuggerTuning = DebuggerKind::LLDB; in DwarfDebug()
/external/llvm/include/llvm/CodeGen/
DCommandFlags.h280 clEnumValN(DebuggerKind::LLDB, "lldb", "lldb"),
/external/swiftshader/third_party/llvm-7.0/llvm/include/llvm/CodeGen/
DCommandFlags.inc257 clEnumValN(DebuggerKind::LLDB, "lldb", "lldb"),
/external/clang/lib/Driver/
DToolChains.h595 return llvm::DebuggerKind::LLDB; in getDefaultDebuggerTuning()

12