- Jul 11, 2012
-
-
Axel Naumann authored
llvm-svn: 160041
-
Rafael Espindola authored
instantiation depends on the template, its arguments and parameters, but not where it is instantiated. llvm-svn: 160034
-
Eric Christopher authored
there's something going on there. Remove the unconditional line entry and only add one if we're emitting cleanups (any other statements would be handled normally). Fixes rdar://9199234 llvm-svn: 160033
-
Eric Christopher authored
llvm-svn: 160032
-
Jordan Rose authored
This is probably not so useful yet because it is not path-sensitive, though it does try to show inlining with indentation. This also adds a dump() method to CallEvent, which should be useful for debugging. llvm-svn: 160030
-
Jordan Rose authored
C++ method calls and C function calls both appear as CallExprs in the AST. This was causing crashes for an object that had a 'free' method. <rdar://problem/11822244> llvm-svn: 160029
-
Richard Smith authored
value-initialization for an array of class type with a trivial default constructor. llvm-svn: 160024
-
Jordan Rose authored
Also contains a number of tweaks to inlining that are necessary for constructors and destructors. (I have this enabled on a private branch, but it is very much unstable.) llvm-svn: 160023
-
Jordan Rose authored
In order to accomplish this, we now build the callee's stack frame as part of the CallEnter node, rather than the subsequent BlockEdge node. This should not have any effect on perceived behavior or diagnostics. This makes it safe to re-enable inlining of member overloaded operators. llvm-svn: 160022
-
Jordan Rose authored
These ProgramPoints are used in inlining calls, and not all calls have associated statements anymore. llvm-svn: 160021
-
Jordan Rose authored
While this work is still fairly tentative (destructors are still left out of the CFG by default), we now handle destructors in the same way as any other calls, instead of just automatically trying to inline them. llvm-svn: 160020
-
Jordan Rose authored
These are currently unused, but are intended to be used in lieu of PreStmt and PostStmt when the call is implicit (e.g. an automatic object destructor). This also modifies the Data1 field of ProgramPoints to allow storing any pointer-sized value, as opposed to only aligned pointers. This is necessary to store SourceLocations. There is currently no BugReporter support for these; they should be skipped over in any diagnostic output. This commit also tags checkers that currently rely on function calls only occurring at StmtPoints. llvm-svn: 160019
-
- Jul 10, 2012
-
-
DeLesley Hutchins authored
llvm-svn: 160018
-
Chad Rosier authored
llvm-svn: 160017
-
Daniel Jasper authored
Reviewers: klimek Differential Revision: http://ec2-50-18-127-156.us-west-1.compute.amazonaws.com/D2 llvm-svn: 160013
-
Benjamin Kramer authored
llvm-svn: 160000
-
Arnaud A. de Grandmaison authored
Adds support for auto-detection of compilation databases, looking in a directory and all its parents. llvm-svn: 159998
-
Axel Naumann authored
Implement UniqueFileContainer::erase(), camelCase, add comment on future optimizations of the cache versus de-optimizations of invalidations. llvm-svn: 159997
-
Anna Zaks authored
PR13319 Reported by Jozsef Mihalicza. llvm-svn: 159996
-
Axel Naumann authored
The consumer might see multiple input files (e.g. for cling) and since r159977 the count is maintained across input files. llvm-svn: 159995
-
Manuel Klimek authored
llvm-svn: 159992
-
Manuel Klimek authored
from a source file and changes clang-check to make use of this. This makes clang-check just work on in-tree builds, and allows easy setup via a symlink per source directory to make clang-check work without any extra configuration. llvm-svn: 159990
-
Manuel Klimek authored
llvm-svn: 159987
-
Chris Lattner authored
*errors* with fixits on them by following the recovery advised by the fixit, but if it is a fixit on a warning, then obviously the AST should be for the code as-written. llvm-svn: 159980
-
Jordan Rose authored
void f(); // expected-note 0+ {{previous declaration is here}} void g(); // expected-note 0-1 {{previous declaration is here}} The old "+" syntax is still an alias for "1+", and single numbers still work. Patch by Andy Gibbs! llvm-svn: 159979
-
Jordan Rose authored
// expected-warning@10 {{some text}} The line number may be absolute (as above), or relative to the current line by prefixing the number with either '+' or '-'. Patch by Andy Gibbs! llvm-svn: 159978
-
Jordan Rose authored
Patch by Andy Gibbs! llvm-svn: 159977
-
Richard Trieu authored
back to regular type printing. llvm-svn: 159976
-
Jordan Rose authored
(per Jean-Daniel's suggestion to keep around an explanation of why direct comparisons on ObjC literals are a bad idea) llvm-svn: 159972
-
Arnaud A. de Grandmaison authored
[cindex.py] Make CompileCommand.arguments usage consistent with CompileCommand.directory and the rest of the python binding Patch by David Röthlisberger llvm-svn: 159970
-
Chad Rosier authored
llvm-svn: 159968
-
Tanya Lattner authored
Silence buildbot so I can figure out the right flag to put this warning under. llvm-svn: 159967
-
Chad Rosier authored
verify this is the correct grouping. llvm-svn: 159966
-
Tanya Lattner authored
llvm-svn: 159965
-
- Jul 09, 2012
-
-
Dmitri Gribenko authored
llvm-svn: 159963
-
Abramo Bagnara authored
llvm-svn: 159961
-
Fariborz Jahanian authored
and similar other keywords. // rdar://10723084 llvm-svn: 159956
-
Matt Beaumont-Gay authored
llvm-svn: 159954
-
Jim Grosbach authored
Lots of tests are using an explicit target triple w/o first checking that the target is actually available. Add a REQUIRES clause to a bunch of them. This should hopefully unbreak bots which don't configure w/ all targets enabled. llvm-svn: 159949
-
Fariborz Jahanian authored
from diagnostics. // rdar://9657485 llvm-svn: 159943
-