llvm-project/clang
Craig Topper 1053e0b27c [RISCV] Use a lambda to avoid having the Support library depend on Option library.
RISCVISAInfo::toFeatures needs to allocate strings using
ArgList::MakeArgString, but toFeatures lives in Support and
MakeArgString lives in Option.

toFeature only has one caller, so the simple fix is to have that
caller pass a lamdba that wraps MakeArgString to break the
dependency.

Differential Revision: https://reviews.llvm.org/D112032
2021-10-18 13:39:37 -07:00
..
INPUTS
bindings
cmake [CMake] Include llvm-libtool-darwin in Fuchsia toolchain 2021-10-07 16:44:40 -07:00
docs Remove also Block-ABI-Apple.txt from the Makefile 2021-10-18 14:56:23 +02:00
examples Revert "Reland "[clang-repl] Re-implement clang-interpreter as a test case."" 2021-10-08 17:43:23 -07:00
include Revert D105169 due to the two-stage failure in ASAN 2021-10-18 23:52:46 +09:00
lib [RISCV] Use a lambda to avoid having the Support library depend on Option library. 2021-10-18 13:39:37 -07:00
runtime
test Fix crash when diagnosing a CTAD failure in an array new expression 2021-10-18 14:01:55 -04:00
tools [git-clang-format] Add --diffstat parameter 2021-10-15 09:56:51 +01:00
unittests [analyzer] Allow matching non-CallExprs using CallDescriptions 2021-10-18 14:57:24 +02:00
utils [ARM] Don't use TARGET_HEADER_BUILTIN in arm_mve_builtins.inc or arm_cde_builtins.inc 2021-10-15 09:11:06 -07:00
www [doc][clang] correct version for p0388 implementation 2021-10-13 04:12:07 -07:00
.clang-format
.clang-tidy
.gitignore
CMakeLists.txt [CMake] Fix typo in error message for LLD in bootstrap builds. 2021-10-06 22:38:12 +05:30
CODE_OWNERS.TXT
INSTALL.txt
LICENSE.TXT
ModuleInfo.txt
NOTES.txt
README.txt

README.txt

//===----------------------------------------------------------------------===//
// C Language Family Front-end
//===----------------------------------------------------------------------===//

Welcome to Clang.  This is a compiler front-end for the C family of languages
(C, C++, Objective-C, and Objective-C++) which is built as part of the LLVM
compiler infrastructure project.

Unlike many other compiler frontends, Clang is useful for a number of things
beyond just compiling code: we intend for Clang to be host to a number of
different source-level tools.  One example of this is the Clang Static Analyzer.

If you're interested in more (including how to build Clang) it is best to read
the relevant web sites.  Here are some pointers:

Information on Clang:             http://clang.llvm.org/
Building and using Clang:         http://clang.llvm.org/get_started.html
Clang Static Analyzer:            http://clang-analyzer.llvm.org/
Information on the LLVM project:  http://llvm.org/

If you have questions or comments about Clang, a great place to discuss them is
on the Clang development mailing list:
  http://lists.llvm.org/mailman/listinfo/cfe-dev

If you find a bug in Clang, please file it in the LLVM bug tracker:
  http://llvm.org/bugs/