search for: udir

...for a given namespace and put them out under a single DW_TAG_namespace DIE, regardless of how many fragments there are in the source. That way, one DW_TAG_imported_module will catch everything (even declarations that come after the "using namespace" lexically, which matches how [namespace.udir]p5 works). So, if Clang is going to use DW_AT_extension to connect separate DIEs, the DW_TAG_imported_module will have to specify the last one in the chain; or, Clang will need to collect these declarations so they can all be emitted under a single namespace DIE. Make sense? --paulr

...c 416K build/tools/clang/test/Modules/Output/extern_c.cpp.tmp 416K build/tools/clang/test/Lexer 416K build/tools/clang/test/Analysis/Output/ctu-main.cpp.tmp 412K build/tools/clang/test/SemaOpenCL 412K build/tools/clang/test/Lexer/Output 412K build/tools/clang/test/Analysis/Output/ctu-main.cpp.tmp/ctudir 408K build/tools/clang/test/SemaOpenCL/Output 400K build/tools/clang/test/PCH/Output/debug-info-pch-path.c.tmp 392K build/lib/Target/PowerPC/TargetInfo 388K build/tools/clang/test/CXX/dcl.decl 384K build/lib/Target/PowerPC/TargetInfo/CMakeFiles 384K build/lib/cmake/llvm 380K build/lib/Target/PowerP...