Skip to content

[clang][deps] Check for "__preprocessed_" before the line-by-line walk - #230

Closed
tagolog wants to merge 1 commit into
mainfrom
scanner-preprocessed-module-check
Closed

tagolog wants to merge 1 commit into
mainfrom
scanner-preprocessed-module-check

Conversation

@tagolog

@tagolog tagolog commented Nov 5, 2026 •

Copy link
Copy Markdown

isPreprocessedModuleFile() scans the whole source line by line,
looking for "__preprocessed_module" or "__preprocessed_import"
directives. This scan is pretty expensive.

Checking for the presence of __preprocessed_ string in the source
speeds up the scan. On swiftlang/llvm-project, a cache hit through
clang-cache with its default inline dependency scan drops

  • from 201.4 to 189.8 ms (-5.7%) on Windows
  • from 107.7 to 100.3 ms (-6.9%) on Linux

@tagolog
tagolog requested review from andreil99, asl and slydiman November 5, 2026 19:19
@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown

Hello @tagolog 👋

Thank you for submitting a Pull Request (PR) to the LLVM Project. Since this is your first PR, here are a few useful links covering our main contribution policies and review practices.

  • All contributions to LLVM must follow our LLVM AI Tool Use Policy. In particular, if you used AI while working on this PR, remember to add a note to the PR description.
  • The LLVM Code-Review Policy and Practices document contains practical information about the PR process, including how patches are reviewed and accepted, and who can review a PR.
  • Our LLVM Developer Policy describes our expectations for code quality, commit summaries and contains notes on our CI system.

Please reply to this message to confirm that you have read these policies, especially the LLVM AI Tool Use Policy, and that any AI tool usage has been noted in the PR description.


Frequently asked questions

How do I add reviewers?

This PR will be automatically labeled, and the relevant teams will be notified. For some parts of the project, reviewers may also be added automatically.

You can also add reviewers manually using the Reviewers section on this page. If you cannot use that section, it is probably because you do not have write permissions for the repository. In that case, you can request a review by tagging reviewers in a comment using @ followed by their GitHub username.

What if there are no comments?

If you have not received any comments on your PR after a week, you can request a review by pinging the PR with a comment such as “Ping”. The common courtesy ping rate is once a week. Please remember that you are asking for volunteer time from other developers.

Are any special GitHub settings required to contribute to LLVM?

We only require contributors to have a public email address associated with their GitHub commits, see this section of LLVM Developer Policy for details.


If you have questions, feel free to leave a comment on this PR, or ask on LLVM Discord or LLVM Discourse.

Thank you,
The LLVM Community

isPreprocessedModuleFile() scans the whole source line by line,
looking for "__preprocessed_module" or "__preprocessed_import"
directives. This scan is pretty expensive.

Add fast path by checking for the presence of "__preprocessed_" string.
On `swiftlang/llvm-project`, a cache hit through
`clang-cache` with its default inline dependency scan drops
- from 201.4 to 189.8 ms (-5.7%) on Windows
- from 107.7 to 100.3 ms (-6.9%) on Linux
@tagolog
tagolog force-pushed the scanner-preprocessed-module-check branch from e3f89de to 04760aa Compare November 6, 2026 01:43

@slydiman slydiman left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@tagolog

tagolog commented Nov 13, 2026

Copy link
Copy Markdown
Author

Implemented in PR 239449

@tagolog tagolog closed this Nov 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants