[clang][modules] Introduce a flag to keep redundant module lookups on relocation checks (#219107) cf8597bd3b87 introduced relocation checks for dependency scans but also disabled it when the modules were built in the same build session for implicit module builds. It turns out downstream projects (using implicit modules) can depend on the relocation check calling `lookupModule` for order-dependent module resolution to hide poorly modularized dependencies within the same build session, since that call loads discovered modules during search. Introduce `-fmodules-force-redundant-lookup` as an escape hatch to maintain preexisting redundant lookup for those projects while keeping the fast path the default for dependency scans.
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.