forked from OSchip/llvm-project
f1a9c4b717
This is unneccesary work. With this change, we skip generating and lexing ~10k of predefines twice. A dumb benchmark of building a preamble for an empty file in a loop shows: - before: 1.90ms/run - after: 1.36ms/run So this should be worth 0.5ms for each AST build and code completion. There can be a functional difference, but it's very minor. If the preamble contains e.g. `#ifndef __llvm__ ... #endif` then before we would not take it. After this change we will take the branch (single-file mode takes all branches with unknown conditions) and so gather different directives. However I think this is negligible: - this is already true of non-builtin macros (from included headers). We've had no complaints. - this affects the baseline and modified in the same way, so only makes a difference transiently when code guarded by such an #ifdef is being edited Differential Revision: https://reviews.llvm.org/D125179 |
||
|---|---|---|
| .. | ||
| clang-apply-replacements | ||
| clang-change-namespace | ||
| clang-doc | ||
| clang-include-fixer | ||
| clang-move | ||
| clang-query | ||
| clang-reorder-fields | ||
| clang-tidy | ||
| clangd | ||
| docs | ||
| include-cleaner | ||
| modularize | ||
| pp-trace | ||
| pseudo | ||
| test | ||
| tool-template | ||
| unittests | ||
| .gitignore | ||
| CMakeLists.txt | ||
| CODE_OWNERS.TXT | ||
| LICENSE.TXT | ||
| README.txt | ||
README.txt
//===----------------------------------------------------------------------===// // Clang Tools repository //===----------------------------------------------------------------------===// Welcome to the repository of extra Clang Tools. This repository holds tools that are developed as part of the LLVM compiler infrastructure project and the Clang frontend. These tools are kept in a separate "extra" repository to allow lighter weight checkouts of the core Clang codebase. This repository is only intended to be checked out inside of a full LLVM+Clang tree, and in the 'tools/extra' subdirectory of the Clang checkout. All discussion regarding Clang, Clang-based tools, and code in this repository should be held using the standard Clang forum: https://discourse.llvm.org/c/clang Code review for this tree should take place on the standard Clang patch and commit lists: http://lists.llvm.org/mailman/listinfo/cfe-commits If you find a bug in these tools, please file it in the LLVM bug tracker: http://llvm.org/bugs/