replica
/
hanchenye-llvm-project
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
hanchenye-llvm-project/clang
History
Adrian Prantl 3be10542af Ensure that the line table for functions with cleanups is sequential. 
If there is cleanup code, the cleanup code gets the debug location of
the closing '}'. The subsequent ret IR-instruction does not get a
debug location. The return _expression_ will get the debug location
of the return statement.

If the function contains only a single, simple return statement,
the cleanup code may become the first breakpoint in the function.
In this case we set the debug location for the cleanup code
to the location of the return statement.

rdar://problem/13442648

llvm-svn: 180932
 		2013-05-02 17:30:20 +00:00
..
INPUTS
…
bindings Fix return type of isBitfield in the binding definition 2013-04-21 18:35:51 +00:00
docs Documentation: Change UTF-8 ellipsis character to ASCII ... sequence 2013-04-27 16:26:29 +00:00
examples The IRReader header is now part of its own library. Update the include 2013-03-26 02:25:54 +00:00
include [analyzer] Consolidate constant evaluation logic in SValBuilder. 2013-05-01 23:10:44 +00:00
lib Ensure that the line table for functions with cleanups is sequential. 2013-05-02 17:30:20 +00:00
runtime Split ubsan runtime into three pieces (clang part): 2013-03-20 23:49:07 +00:00
test Ensure that the line table for functions with cleanups is sequential. 2013-05-02 17:30:20 +00:00
tools [analyzer] Finally make c++-analyzer 'executable' again. 2013-05-02 01:57:58 +00:00
unittests When deducing an 'auto' type, don't modify the type-as-written. 2013-04-30 21:23:01 +00:00
utils [neonemitter tests] Change triple of emitted tests to thumbv7s to match the target cpu being swift. Also specify the target-abi to apcs-gnu. 2013-04-25 00:10:14 +00:00
www Implement C++1y decltype(auto). 2013-04-26 16:15:35 +00:00
.arcconfig Add .arcconfig to the repository. Useful if someone wants to use phabricator's command line tool. 2012-12-01 12:08:08 +00:00
.gitignore Reverted unintendedly-committed file. 2013-01-31 19:05:31 +00:00
CMakeLists.txt cmake: Only add -pedantic if LLVM didn't add it. Don't unconditionally add 2013-04-22 14:51:21 +00:00
CODE_OWNERS.TXT Duplicate some common owners between Clang and LLVM. 2012-11-27 00:48:12 +00:00
INSTALL.txt Minor tweak to install docs 2013-02-05 22:01:16 +00:00
LICENSE.TXT Update the copyright coredits -- Happy new year 2013! 2013-01-01 10:00:19 +00:00
Makefile
…
ModuleInfo.txt
…
NOTES.txt Remove an uninteresting note 2013-02-05 21:13:55 +00:00
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/