llvm-project/clang
Petr Hosek 2482b3a967 [Driver] Always use --as-needed with libunwind
With libgcc, we follow the behavior of GCC for backwards compatibility,
only using --as-needed in the non-C++ mode.

With libunwind, there are no backward compatibility requirements so we
can always use --as-needed on all supported platforms.

Differential Revision: https://reviews.llvm.org/D128841
2022-06-29 20:41:19 +00:00
..
bindings [OpenMP] Initial parsing and sema for 'parallel masked' construct 2022-06-16 18:01:15 -07:00
cmake [CMake][compiler-rt] Provide a dedicated option for LLVM unwinder 2022-06-14 17:26:25 +00:00
docs [clang][dataflow] Delete SourceLocationsLattice 2022-06-29 20:14:07 +00:00
examples
include [clang][dataflow] Delete SourceLocationsLattice 2022-06-29 20:14:07 +00:00
lib [Driver] Always use --as-needed with libunwind 2022-06-29 20:41:19 +00:00
runtime Generalize "check-all" umbrella targets, use for check-clang-tools 2022-05-06 12:30:49 +02:00
test [Driver] Always use --as-needed with libunwind 2022-06-29 20:41:19 +00:00
tools [LinkerWrapper] Change wrapping to include jumps for other variables 2022-06-29 14:48:39 -04:00
unittests [clang][dataflow] Delete SourceLocationsLattice 2022-06-29 20:14:07 +00:00
utils [clang] Don't use Optional::hasValue (NFC) 2022-06-25 22:26:24 -07:00
www [Clang] Mark consteval as supported in Clang 15 [NFC] 2022-06-29 22:23:17 +02:00
.clang-format
.clang-tidy
.gitignore
CMakeLists.txt Revert "[cmake] Don't export `LLVM_TOOLS_INSTALL_DIR` anymore" 2022-06-10 19:26:12 +00:00
CODE_OWNERS.TXT
INSTALL.txt
LICENSE.TXT
ModuleInfo.txt
NOTES.txt
README.txt Replace links to archived mailing lists by links to Discourse forums 2022-03-23 10:10:20 -04:00

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 forums:
  https://discourse.llvm.org/c/clang/

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