fce3a66f5e
When the same name is USE-associated with two or more distinct ultimate symbols, and they are not both generic procedure interfaces, it's not an error unless the name is actually referenced in the scope. But when the scope is itself a module or submodule, our module files don't preserve the error for later diagnosis -- instead, the UseErrorDetails symbol that serves as a "poison pill" in case of later use is discarded when the module file is generated. So emit additional USE statements to the module file so that a UseErrorDetails symbol is created anew when the module file is read.
The LLVM Compiler Infrastructure
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.
Getting the Source Code and Building LLVM
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.
Getting in touch
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.