[LangRef] Clarify norecurse attribute definition when a function could occur in a cycle in dynamic call-graph (#157087) Update the definition of the `norecurse` attribute to forbid marking a function as `norecurse` if any call path from its body may reach it (possibly through an external function without a visible definition). This makes it clear that `norecurse` excludes both direct and mutual recursion, even when recursion could arise through callees in separate modules. This kind of scenario only arises when norecurse is forced through a llvm user option `-mllvm -force-attribute=<fname>:norecurse` There are a few examples in https://github.com/llvm/llvm-project/issues/157081 which shows that the function attribute inference incorrectly infers norecurse when the behavior (as per new definition) is not enforced.
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.