hanchenye-llvm-project/clang
Mirko Brkusanin 4b63ca1379 [Mips] Use appropriate private label prefix based on Mips ABI
MipsMCAsmInfo was using '$' prefix for Mips32 and '.L' for Mips64
regardless of -target-abi option. By passing MCTargetOptions to MCAsmInfo
we can find out Mips ABI and pick appropriate prefix.

Tags: #llvm, #clang, #lldb

Differential Revision: https://reviews.llvm.org/D66795
2019-10-23 12:24:35 +02:00
..
INPUTS
bindings [TestCommit] Trivial change to test commit access. 2019-09-19 09:24:42 +00:00
cmake [CMake] Clang: Don't use object libraries with Xcode 2019-10-04 18:17:58 +00:00
docs [Implicit Modules] Add -cc1 option -fmodules-strict-context-hash which includes search paths and diagnostics. 2019-10-21 22:51:13 +00:00
examples Fixup build of clang-interpreter example after change in r370122. 2019-08-28 02:13:24 +00:00
include [c++2a] Allow comparison functions to be explicitly defaulted. 2019-10-22 18:16:17 -07:00
lib [Mips] Use appropriate private label prefix based on Mips ABI 2019-10-23 12:24:35 +02:00
runtime
test [c++2a] Allow comparison functions to be explicitly defaulted. 2019-10-22 18:16:17 -07:00
tools [Mips] Use appropriate private label prefix based on Mips ABI 2019-10-23 12:24:35 +02:00
unittests [FrontendTests] Try again to make test not write an output file 2019-10-22 08:44:34 +00:00
utils [analyzer] exploded-graph-rewriter: Rename Environment to Expressions. 2019-10-18 20:15:41 +00:00
www [c++20] Add rewriting from comparison operators to <=> / ==. 2019-10-19 00:04:43 +00:00
.arcconfig
.clang-format
.clang-tidy
.gitignore
CMakeLists.txt [clang] [cmake] Support LLVM_DISTRIBUTION_COMPONENTS in stand-alone build 2019-10-07 18:14:56 +00:00
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/