commit | 37180ed7435d28282ff4ccc9fbcbed04124ef8c0 | [log] [tgz] |
---|---|---|
author | Peter Klausler <35819229+klausler@users.noreply.github.com> | Mon Jan 29 14:36:37 2024 -0800 |
committer | GitHub <noreply@github.com> | Mon Jan 29 14:36:37 2024 -0800 |
tree | 5a78c34ae35feeb86b41ec07ebfe4f3da82f0d8d | |
parent | d83c97714756e828c9c7091aa8294e022c93a454 [diff] |
[flang] Turn "error" cases into warning for "indistinguishable" specific procedures (#79621) When a generic procedure interface, either declared or the result of merging two use-associated generics, has two specific procedures that are not distinguishable according to the rules in F'2023 subclause 15.4.3.4.5, emit a portability warning rather than a hard error message. The rules in that subclause are not adequate to detect pairs of specific procedures that admit an ambiguous reference, as demonstrated by a case that arose in pFUnit. Further, these distinguishability checks, even if sufficient to the task of detecting pairs of specifics capable of ambiguous references, should only apply to pairs where *every* reference would have to be ambiguous -- and this can and is validated at every reference anyway. Last, only XLF enforces these incomplete and needless distinguishability rules -- every other compiler seems to just check that each procedure reference resolves to exactly one specific procedure. If the standard were to complete lose subclause 15.4.3.4.5 and its related note (C.11.6) -- which admits that the rules are incomplete! -- and simply require that each generic procedure reference resolve unambiguously to exactly one specific, nobody would miss them. This patch changes this compiler to give them lip service when requested, but they are now otherwise ignored.
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.