maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang
History
Jordan Rose 2fa69ef934 Add new tool 'diag-build' for showing enabled warnings in a project. 
diag-build acts as a wrapper for 'diagtool show-enabled', in the same way
that scan-build acts as a wrapper for the static analyzer. The common case is
simple: use 'diag-build make' or 'diag-build xcodebuild' to list the warnings
enabled for the first compilation command we see. Other build systems require
you to manually specify "dry-run" and "use $CC and $CXX"; if there is a build
system you are interested in, please add it to the switch statement.

diag-build is fairly stupid right now, but it serves its basic purpose.
Hopefully it can grow to meet any additional requirements.

llvm-svn: 158682
 		2012-06-18 21:31:37 +00:00
..
INPUTS all-std-headers.cpp: Include the C++11 headers when building with clang 2012-04-13 03:39:16 +00:00
bindings/python [clang.py] Implement SourceLocation.from_offset 2012-06-11 11:11:48 +00:00
docs document _has_feature(objc_default_synthesize_properties). 2012-06-18 17:13:17 +00:00
examples Honour CLANG_BUILD_EXAMPLES correctly, by setting the directory's 2012-05-03 19:11:45 +00:00
include Move a few static functions from DiagnosticRenderer.cpp into SourceManager. 2012-06-18 20:12:05 +00:00
lib [analyzer] Add a comment: why we treat array compound literals as lvalues. 2012-06-18 21:31:27 +00:00
runtime [tsan] add ThreadSanitizer linker flags on Linux and also copy the tsan-rt into the appropriate place at build time 2012-05-16 06:36:00 +00:00
test Allow internal decls in inline functions if the function is in the main file. 2012-06-18 17:49:58 +00:00
tools Add new tool 'diag-build' for showing enabled warnings in a project. 2012-06-18 21:31:37 +00:00
unittests ToolingTest.cpp: Fix r158592, runToolOnCode.FindsNoTopLevelDeclOnEmptyCode on msvc. LangOpts.MicrosoftExt still appends "class type_info;". 2012-06-16 06:04:05 +00:00
utils Handle C++11 attribute namespaces automatically. 2012-06-18 16:13:52 +00:00
www Make the analyzer site a single point of reference for info 2012-06-16 00:30:21 +00:00
.gitignore Revert "Test commit" 2011-10-24 10:03:25 +00:00
CMakeLists.txt Zap the /Za compiler switch from MSVC projects, the option is considered harmful even by Microsoft people and clang won't build using the MSVC 2012 RC if not removed. 2012-06-06 12:00:10 +00:00
INSTALL.txt
…
LICENSE.TXT Happy new year 2012! 2012-01-01 08:16:56 +00:00
Makefile
…
ModuleInfo.txt
…
NOTES.txt Add a note about a missing optimization in the case of virtual 2012-03-30 04:25:03 +00:00
README.txt commit access verified, revert change 2012-03-06 22:55:51 +00: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 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/