commit | d0708e6285b88510649722fe8e6832ee1d7abfb1 | [log] [tgz] |
---|---|---|
author | Peter Klausler <35819229+klausler@users.noreply.github.com> | Mon Jan 15 11:37:46 2024 -0800 |
committer | GitHub <noreply@github.com> | Mon Jan 15 11:37:46 2024 -0800 |
tree | 437f0ba9bc2aebf56ceaebc711efd9a5758db7fc | |
parent | 6719a5a3f6744efdb31095933e272163b294c8f7 [diff] |
[flang] Refine IMPORT processing in module file generation (#77133) Procedure interfaces emitted to module files are including IMPORT statements for some symbols that don't need to be imported (base types and procedure interfaces for components of imported derived types) and omitting others (procedure interfaces for bindings in locally-defined derived types that are material to the interface).
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.