- Apr 02, 2009
-
-
Douglas Gregor authored
definition, warn if there are too many/too few function call arguments. llvm-svn: 68318
-
Daniel Dunbar authored
llvm-svn: 68316
-
Ted Kremenek authored
llvm-svn: 68302
-
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
-
Douglas Gregor authored
llvm-svn: 68289
-
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
-
Ted Kremenek authored
llvm-svn: 68282
-
Ted Kremenek authored
llvm-svn: 68281
-
Anders Carlsson authored
llvm-svn: 68280
-
Douglas Gregor authored
llvm-svn: 68279
-
Douglas Gregor authored
llvm-svn: 68278
-
Chris Lattner authored
"The code was doing "if (End+NumInputs > Capacity) ...". If End is close to 0xFFFFFFFF and NumInputs is large, it'll overflow, the condition will come out false, and the vector won't grow to accommodate the new elements, and the program will crash in memmove." Patch by Jeffrey Yasskin! llvm-svn: 68277
-
Ted Kremenek authored
llvm-svn: 68276
-
Ted Kremenek authored
llvm-svn: 68275
-
Ted Kremenek authored
llvm-svn: 68274
-
Ted Kremenek authored
llvm-svn: 68273
-
Mike Stump authored
Eventually, would be nice to be able to run these modifications even when we don't want the warning or errors for the actual diagnostic. llvm-svn: 68272
-
Zhongxing Xu authored
llvm-svn: 68271
-
Mike Stump authored
llvm-svn: 68270
-
Mikhail Glushenkov authored
llvm-svn: 68269
-
Douglas Gregor authored
llvm-svn: 68268
-
Mike Stump authored
better name) is the option that SmallTalk can use to intercept all overflows, including unsigned. I added some testcases so we don't break anything. Also included is another patch from David for += and friends. llvm-svn: 68267
-
Ted Kremenek authored
llvm-svn: 68264
-
Mike Stump authored
llvm-svn: 68263
-
Owen Anderson authored
llvm-svn: 68262
-
Douglas Gregor authored
llvm-svn: 68261
-
Daniel Dunbar authored
calling gcc in generic configurations. llvm-svn: 68260
-
Fariborz Jahanian authored
class which was exposed by implementation of objc2's nonfragile abi code gen. llvm-svn: 68259
-
Bill Wendling authored
llvm-svn: 68258
-
Douglas Gregor authored
Plus, reword a extension warnings to avoid talking about "ISO C" when the extension might also be available in C++ or C++0x. llvm-svn: 68257
-
Devang Patel authored
llvm-svn: 68254
-
Chris Lattner authored
llvm-svn: 68253
-
- Apr 01, 2009
-
-
Daniel Dunbar authored
- The code is silly, I'm just amusing myself. Rewrite to be efficient if you like. :) Also, if you wish to debate the proper names of the triple components I'm all ears. llvm-svn: 68252
-
Douglas Gregor authored
failures that involve malformed types, e.g., "typename X::foo" where "foo" isn't a type, or "std::vector<void>" that doens't instantiate properly. Similarly, be a bit smarter in our handling of ambiguities that occur in Sema::getTypeName, to eliminate duplicate error messages about ambiguous name lookup. This eliminates two XFAILs in test/SemaCXX, one of which was crying out to us, trying to tell us that we were producing repeated error messages. llvm-svn: 68251
-
Misha Brukman authored
llvm-svn: 68250
-
Misha Brukman authored
llvm-svn: 68249
-