Lines Matching +refs:clang +refs:format +refs:extract

12 information in LLVM.  It describes the :ref:`actual format that the LLVM debug
13 information takes <format>`, which is useful for those interested in creating
49 :ref:`implementation-defined format <ccxx_frontend>` (the C/C++ front-end
69 the Microsoft debug info format, which is usable with Microsoft debuggers such
70 as Visual Studio and WinDBG. LLVM's debug information format is mostly derived
134 Debugging information format
215 In order to handle this, the LLVM debug format uses the metadata attached to
264 …!0 = !DICompileUnit(language: DW_LANG_C99, file: !1, producer: "clang version 3.7.0 (trunk 231150)…
274   !10 = !{!"clang version 3.7.0 (trunk 231150) (llvm/trunk 231154)"}
347 The C and C++ front-ends represent information about the program in a format
371 instruction.  One can extract line number information encoded in LLVM IR using
411                       "clang version 3.7.0 (trunk 231150) (llvm/trunk 231154)",
476 Debugging information format
492 information generated by compiler in DWARF format.  The format does not support
704 clang.
735 uses clang for its expression parsing where LLDB acts as a PCH.  LLDB is then
738 tables.  Since clang asks a lot of questions when it is parsing an expression,
749 * Have a format that can be mapped into memory from disk and used as is
751 * Extensible table format so these tables can be made by many producers
755 Table size is important and the accelerator table format should allow the reuse
1003 The header has a fixed part, and the specialized part.  The exact format of the
1349 LLVM supports emitting CodeView, the Microsoft debug info format, and this
1355 CodeView as a format is clearly oriented around C++ debugging, and in C++, the
1400     $ clang -g -gcodeview --target=x86_64-windows-msvc foo.cpp -S -emit-llvm