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
132 Debugging information format
213 In order to handle this, the LLVM debug format uses the metadata attached to
262 …!0 = !DICompileUnit(language: DW_LANG_C99, file: !1, producer: "clang version 3.7.0 (trunk 231150)…
272 !10 = !{!"clang version 3.7.0 (trunk 231150) (llvm/trunk 231154)"}
345 The C and C++ front-ends represent information about the program in a format
369 instruction. One can extract line number information encoded in LLVM IR using
409 "clang version 3.7.0 (trunk 231150) (llvm/trunk 231154)",
474 Debugging information format
490 information generated by compiler in DWARF format. The format does not support
696 clang.
727 uses clang for its expression parsing where LLDB acts as a PCH. LLDB is then
730 tables. Since clang asks a lot of questions when it is parsing an expression,
741 * Have a format that can be mapped into memory from disk and used as is
743 * Extensible table format so these tables can be made by many producers
747 Table size is important and the accelerator table format should allow the reuse
995 The header has a fixed part, and the specialized part. The exact format of the