Adrian Prantl 717764717b Add a DIModule metadata node to the IR. ... It is meant to be used to record modules @imported by the current compile unit, so a debugger an import the same modules to replicate this environment before dropping into the expression evaluator. DIModule is a sibling to DINamespace and behaves quite similarly. In addition to the name of the module it also records the module configuration details that are necessary to uniquely identify the module. This includes the configuration macros (e.g., -DNDEBUG), the include path where the module.map file is to be found, and the isysroot. The idea is that the backend will turn this into a DW_TAG_module. http://reviews.llvm.org/D9614 rdar://problem/20965932 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@241017 91177308-0d34-0410-b5e6-96231b3b80d8		2015-06-29 23:03:47 +00:00
..
BitcodeWriter.cpp	Add a DIModule metadata node to the IR.	2015-06-29 23:03:47 +00:00
BitcodeWriterPass.cpp	Revert r240137 (Fixed/added namespace ending comments using clang-tidy. NFC)	2015-06-23 09:49:53 +00:00
BitWriter.cpp
CMakeLists.txt
LLVMBuild.txt
Makefile
ValueEnumerator.cpp	Use foreach loop over constant operands. NFC.	2015-06-25 20:51:38 +00:00
ValueEnumerator.h	Revert r240137 (Fixed/added namespace ending comments using clang-tidy. NFC)	2015-06-23 09:49:53 +00:00