maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang
History
Saleem Abdulrasool 42e4b5997a clang: forward -no-integrated-as from the driver 
Forward the -no-integrated-as option to -cc1 rather than simply invoking the
appropriate tool.  This is useful since this option has been overloaded to
permit disabling of parsing inline assembly at the MC layer.

This re-applies the previous version of the patch with a renaming of the driver
option to the public name rather than the internal name (-target vs -triple).
The actual failure is fixed separately of an overly aggressive negative pattern
match in the MIPS driver tests.  It also fixes the incorrect test for targets
that have the integrated assembler disabled by default.

llvm-svn: 201960
 		2014-02-22 23:37:58 +00:00
..
INPUTS
…
bindings [libclang/python] Use a Python standard library module to create a temporary file. 2014-02-20 07:24:03 +00:00
docs Adding manual headings to the new capability attributes' documentation. 2014-02-22 19:04:55 +00:00
examples [CMake] Get rid of explicit dependencies to include/clang/*.inc and introduce CLANG_TABLEGEN_TARGETS. 2014-02-21 07:59:59 +00:00
include Adding manual headings to the new capability attributes' documentation. 2014-02-22 19:04:55 +00:00
lib clang: forward -no-integrated-as from the driver 2014-02-22 23:37:58 +00:00
runtime Macho-embedded: rename compiler-rt support from Darwin-embedded 2014-01-21 12:38:19 +00:00
test clang: forward -no-integrated-as from the driver 2014-02-22 23:37:58 +00:00
tools [CMake] libclang: Use llvm_add_library(SHARED STATIC). 2014-02-21 15:34:01 +00:00
unittests Correctly set brace range for CXXConstructExprs formed by list initialization. 2014-02-22 02:59:41 +00:00
utils Moving the documentation for the type safety checking attributes into AttrDocs. If a custom heading is provided, do not automatically generate the alternate spelling list. This is necessary because some attributes have distinct semantic spellings and meanings, but use the same semantic attribute internally. Such attributes should have multiple elements in their documentation list, but not show all spellings. At some point, it would be nice to have a way to attach the documentation element to a specific spelling for these cases. 2014-02-21 14:14:04 +00:00
www [analyzer] post analyzer build checker-276 2014-02-19 08:09:22 +00:00
.arcconfig
…
.clang-format Switch the default mode for clang-format to '-file'. Make 'LLVM' the 2013-09-02 07:42:02 +00:00
.gitignore
…
CMakeLists.txt [CMake] Get rid of explicit dependencies to include/clang/*.inc and introduce CLANG_TABLEGEN_TARGETS. 2014-02-21 07:59:59 +00:00
CODE_OWNERS.TXT Adding myself as the code owner for the attribute subsystem. 2014-01-13 22:23:27 +00:00
INSTALL.txt
…
LICENSE.TXT Update the copyright credits -- Happy new year 2014! 2014-01-01 08:27:31 +00:00
Makefile Define ENABLE_CLANG_EXAMPLES instead of relying on BUILD_EXAMPLES 2014-01-08 13:00:32 +00:00
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.cs.uiuc.edu/mailman/listinfo/cfe-dev

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