search for: llvm_redundant_head

...; unittests/CodeGen/CodeGenExternalTest.cpp 3.43 2.52 -26.5% > tools/libclang/CXStoredDiagnostic.cpp 1.67 1.26 -24.8% > tools/clang-func-mapping/ClangFnMapGen.cpp 2.48 1.89 -23.8% > > Full list: > <clang.txt> > > The corresponding patches (careful, they are big): > <llvm_redundant_headers.patch> > <clang_redundant_headers.patch> > > *Methodology* > My tool took the compile_commands.json from LLVM build and iterated over > files trying to remove redundant headers. To find which header files could > be removed it scanned the file for "#include"...

...eGen/CodeGenExternalTest.cpp 3.43 2.52 -26.5% > tools/libclang/CXStoredDiagnostic.cpp 1.67 1.26 -24.8% > tools/clang-func-mapping/ClangFnMapGen.cpp 2.48 1.89 -23.8% > > Full list: > > <clang.txt> > > > The corresponding patches (careful, they are big): > > <llvm_redundant_headers.patch> > <clang_redundant_headers.patch> > > > *Methodology* > My tool took the compile_commands.json from LLVM build and iterated over > files trying to remove redundant headers. To find which header files could > be removed it scanned the file for "#include&...

...05/981e50d6/attachment-0003.txt> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20171205/981e50d6/attachment-0007.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: llvm_redundant_headers.patch Type: application/octet-stream Size: 293711 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20171205/981e50d6/attachment-0002.obj> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/...

...08/8b360593/attachment-0003.txt> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20171208/8b360593/attachment-0007.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: llvm_redundant_headers.patch Type: application/octet-stream Size: 153043 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20171208/8b360593/attachment-0002.obj> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/...

...ntiki.cpp 0.53 0.38 -28.1% 42.4 38.0 -10.5% > unittests/Tooling/RefactoringActionRulesTest.cpp 3.22 2.34 -27.5% 108.3 > 90.0 -16.9% > lib/Serialization/GeneratePCH.cpp 2.38 1.78 -25.1% 83.8 71.1 -15.1% > > Full list: > <clang.txt> > > > The updated patches: > <llvm_redundant_headers.patch> > <clang_redundant_headers.patch> > > Thanks, > Michael > > On Dec 8, 2017, at 9:20 AM, Quentin Colombet via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > On Dec 6, 2017, at 1:17 PM, Matthias Braun via llvm-dev < > llvm-dev a...

...% >> tools/libclang/CXStoredDiagnostic.cpp 1.67 1.26 -24.8% >> tools/clang-func-mapping/ClangFnMapGen.cpp 2.48 1.89 -23.8% >> >> Full list: >> >> <clang.txt> >> >> >> The corresponding patches (careful, they are big): >> >> <llvm_redundant_headers.patch> >> <clang_redundant_headers.patch> >> >> >> *Methodology* >> My tool took the compile_commands.json from LLVM build and iterated over >> files trying to remove redundant headers. To find which header files could >> be removed it scanned...

...t.cpp 3.43 2.52 -26.5% >> tools/libclang/CXStoredDiagnostic.cpp 1.67 1.26 -24.8% >> tools/clang-func-mapping/ClangFnMapGen.cpp 2.48 1.89 -23.8% >> >> Full list: >> <clang.txt> >> >> The corresponding patches (careful, they are big): >> <llvm_redundant_headers.patch> >> <clang_redundant_headers.patch> >> >> Methodology >> My tool took the compile_commands.json from LLVM build and iterated over files trying to remove redundant headers. To find which header files could be removed it scanned the file for "#include&...

- We do indeed have a lot of unnecessary includes around in llvm (or pretty much any other C++ project for that matter). - I want faster builds. - The only way to reliably fight this is indeed automatic tools. - Having the right amount of includes also has documentation value and ideally let's you understand the structure of your project. - However relying on transitive includes works contrary