- Apr 04, 2009
-
-
Anton Korobeynikov authored
llvm-svn: 68414
-
Anton Korobeynikov authored
llvm-svn: 68413
-
Anders Carlsson authored
llvm-svn: 68412
-
Anders Carlsson authored
llvm-svn: 68411
-
Daniel Dunbar authored
arguments" warning. llvm-svn: 68410
-
- Apr 03, 2009
-
-
Fariborz Jahanian authored
used in a class which declares a property of the same name. This should not result in an unimplemented method warning. llvm-svn: 68409
-
Chris Lattner authored
llvm-svn: 68407
-
Ted Kremenek authored
llvm-svn: 68406
-
Daniel Dunbar authored
need to do anything special to support this. llvm-svn: 68403
-
Ted Kremenek authored
the subtle ownership issues of such objects. llvm-svn: 68397
-
Chris Lattner authored
llvm-svn: 68395
-
Steve Naroff authored
llvm-svn: 68379
-
Zhongxing Xu authored
when creating symbolic values, we distinguish between location and non-location values. For location values, we create a symbolic region instead of a loc::SymbolVal. llvm-svn: 68373
-
Anders Carlsson authored
Ignore plus operands when looking up the operand number from a named operand. This matches llvm-gcc and fixes PR3908. llvm-svn: 68371
-
Fariborz Jahanian authored
llvm-svn: 68369
-
Daniel Dunbar authored
wasn't being forwarded. llvm-svn: 68365
-
Daniel Dunbar authored
string literals. llvm-svn: 68363
-
Douglas Gregor authored
llvm-svn: 68354
-
Douglas Gregor authored
llvm-svn: 68346
-
Ted Kremenek authored
llvm-svn: 68345
-
- Apr 02, 2009
-
-
Ed Schouten authored
Approved by: ddunbar llvm-svn: 68343
-
Douglas Gregor authored
applies fix-its to error messages that occur at that specific location in the program. llvm-svn: 68342
-
Fariborz Jahanian authored
objc's continuation class. llvm-svn: 68339
-
-
Daniel Dunbar authored
- Patch by Pawel Worach! llvm-svn: 68332
-
Mike Stump authored
llvm-svn: 68330
-
Sanjiv Gupta authored
Don't use static globals for params as it confuses the optimzer that their values are never being used in the function. llvm-svn: 68328
-
Douglas Gregor authored
scenes, using the underlying diagnostic client to format the messages. llvm-svn: 68324
-
Douglas Gregor authored
llvm-svn: 68322
-
Anders Carlsson authored
llvm-svn: 68321
-
Anders Carlsson authored
llvm-svn: 68320
-
Anders Carlsson authored
llvm-svn: 68319
-
Douglas Gregor authored
definition, warn if there are too many/too few function call arguments. llvm-svn: 68318
-
Daniel Dunbar authored
llvm-svn: 68316
-
Chris Lattner authored
llvm-svn: 68301
-
Anders Carlsson authored
llvm-svn: 68300
-
Ted Kremenek authored
long-term strategy, but this should work for now. llvm-svn: 68297
-
Ted Kremenek authored
can use a PathLocation after any reference Stmts are reclaimed, flattenLocation() converts those references to statements to source ranges. llvm-svn: 68292
-
Chris Lattner authored
of the range is now the ';' location. For something like this: $ cat t2.c #define bool int void f(int x, int y) { bool b = !x && y; } We used to produce: $ clang-cc t2.c -ast-dump typedef char *__builtin_va_list; void f(int x, int y) (CompoundStmt 0x2201f10 <t2.c:3:22, line:5:1> (DeclStmt 0x2201ef0 <line:2:14> <---- 0x2201a20 "int b = (BinaryOperator 0x2201ed0 <line:4:10, col:16> 'int' '&&' (UnaryOperator 0x2201e90 <col:10, col:11> 'int' prefix '!' (DeclRefExpr 0x2201c90 <col:11> 'int' ParmVar='x' 0x2201a50)) (DeclRefExpr 0x2201eb0 <col:16> 'int' ParmVar='y' 0x2201e10))") Now we produce: $ clang-cc t2.c -ast-dump typedef char *__builtin_va_list; void f(int x, int y) (CompoundStmt 0x2201f10 <t2.c:3:22, line:5:1> (DeclStmt 0x2201ef0 <line:2:14, line:4:17> <------ 0x2201a20 "int b = (BinaryOperator 0x2201ed0 <col:10, col:16> 'int' '&&' (UnaryOperator 0x2201e90 <col:10, col:11> 'int' prefix '!' (DeclRefExpr 0x2201c90 <col:11> 'int' ParmVar='x' 0x2201a50)) (DeclRefExpr 0x2201eb0 <col:16> 'int' ParmVar='y' 0x2201e10))") llvm-svn: 68288
-
Ted Kremenek authored
llvm-svn: 68283
-