aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/CommandFlags.cpp
diff options
context:
space:
mode:
authorAaron Ballman <aaron@aaronballman.com>2025-03-12 08:02:44 -0400
committerGitHub <noreply@github.com>2025-03-12 08:02:44 -0400
commit1d89d7d5d76e391b035f50343e2a4890506c6f2b (patch)
treef5c2f95f5a395b62e0247e493f0d81c7175cbdc7 /llvm/lib/CodeGen/CommandFlags.cpp
parent6bf0c4648eeac4f4fda57b6be76e2741c2506478 (diff)
downloadllvm-1d89d7d5d76e391b035f50343e2a4890506c6f2b.zip
llvm-1d89d7d5d76e391b035f50343e2a4890506c6f2b.tar.gz
llvm-1d89d7d5d76e391b035f50343e2a4890506c6f2b.tar.bz2
[Docs] Explain how to propose an extension in Clang (#130803)
We have a list of criteria for proposing an extension in Clang, but we do not have any documentation about how to propose an extension. This adds some basic documentation about how we run RFCs in Clang, as well as adds a list of Clang Area Team members in support of the process. It could be argued that this should be documented for the entire LLVM Project, however, other parts of the project have different rules for proposing extensions. (Extending libc++ is a different proposition than extending LLVM, than extending MLIR, than extending Clang, etc.) We may want to introduce high-level documentation for the LLVM Project, but that is a bigger project and we already have the documentation in Clang about criteria for extensions. So it seems reasonable to add some lightweight documentation specific to Clang until we determine what to do at the whole project level.
Diffstat (limited to 'llvm/lib/CodeGen/CommandFlags.cpp')
0 files changed, 0 insertions, 0 deletions