- Oct 20, 2012
-
-
Richard Smith authored
initialized by a reference constant expression. Our odr-use modeling still needs work here: we don't yet implement the 'set of potential results of an expression' DR. llvm-svn: 166361
-
Argyrios Kyrtzidis authored
macro expansion ranges, make sure to check all the FileID entries that are contained in the spelling range of the expansion for the macro argument. Fixes rdar://12537982 llvm-svn: 166359
-
Chad Rosier authored
llvm-svn: 166358
-
Chad Rosier authored
llvm-svn: 166353
-
Michael J. Spencer authored
llvm-svn: 166348
-
Michael J. Spencer authored
llvm-svn: 166347
-
Shuxin Yang authored
llvm-svn: 166345
-
- Oct 19, 2012
-
-
Chad Rosier authored
llvm-svn: 166317
-
Chad Rosier authored
llvm-svn: 166312
-
Eli Friedman authored
llvm-svn: 166311
-
Chad Rosier authored
llvm-svn: 166310
-
Daniel Dunbar authored
llvm-svn: 166304
-
Daniel Dunbar authored
- Also, lit is going to get a valgrind feature, instead. llvm-svn: 166301
-
Daniel Dunbar authored
- We create two TargetLoweringInfo instances for different pass managers, and they weren't consistent (the one for codegen didn't have the right info). I'm not sure this mattered anywhere in practice. llvm-svn: 166299
-
Shuxin Yang authored
llvm-svn: 166298
-
David Blaikie authored
Suggestion from Matt Beaumont-Gay reviewing r165283. llvm-svn: 166296
-
Chad Rosier authored
llvm-svn: 166293
-
Dmitri Gribenko authored
llvm-svn: 166287
-
Jordan Rose authored
Also, unify ObjCShouldCallSuperDealloc and ObjCShouldCallSuperFinalize. The two have identical behavior and will never be active at the same time. There's one last simplification now, which is that if we see a call to [super foo] and we are currently in a method named 'foo', we will /unconditionally/ clear the ObjCShouldCallSuper flag, rather than check first to see if we're in a method where calling super is required. There's no reason to pay the extra lookup price here. llvm-svn: 166285
-
Andy Gibbs authored
Change VerifyDiagnosticConsumer so that it *must* contain at least one "expected-*" directive. As a result, for test-cases that are not expected to generate any diagnostics, an additional directive "expected-no-diagnostics" has been implemented which can then be included in such test-cases. This new directive may not be used in conjunction with any other "expected-*" directive. This change was initially proposed as a solution to the problem highlighted by check-in r164677, i.e. that -verify will not cause a test-case failure where the compile command does not actually reference the file. Patch reviewed by David Blaikie. llvm-svn: 166281
-
Andy Gibbs authored
Prior to adding the new "expected-no-diagnostics" directive to VerifyDiagnosticConsumer, make the necessary adjustment to 580 test-cases which will henceforth require this new directive. llvm-svn: 166280
-
Andy Gibbs authored
Fix directive parsing in VerifyDiagnosticConsumer so that it ensures that "expected" is at the start of the word and will no longer accept typos such as "junkexpected-*" as a valid "expected-*" directive. A very few test-cases had to be amended to adhere to the new rule. Patch reviewed by David Blaikie. llvm-svn: 166279
-
Nick Lewycky authored
Richard has an unreduced testcase to work with. llvm-svn: 166272
-
Kostya Serebryany authored
llvm-svn: 166271
-
Richard Smith authored
const non-volatile global does. llvm-svn: 166269
-
Richard Smith authored
class, diagnose if the qualified-id instantiates to a non-static class member. llvm-svn: 166268
-
Rafael Espindola authored
constructors. When I first moved regparm support to TargetInfo.cpp I tried to isolate it in classifyArgumentTypeWithReg, but it is actually a lot easier to flip the code around and check for regparm at the end of the decision tree. Without this refactoring classifyArgumentTypeWithReg would have to duplicate the logic about when to use non-byval indirect arguments. llvm-svn: 166266
-
Craig Topper authored
Teach getColumnNumber to use the line cache to get the start of the line if its on the same line as the last call to getLineNumber. Prevents needing to scan backwards for the new line. Fixes PR14106. llvm-svn: 166265
-
Nadav Rotem authored
llvm-svn: 166263
-
NAKAMURA Takumi authored
clang/test/Index/annotate-comments.cpp: Relax the expression to be matched to -fms-compatibility. Then XFAIL can be removed. FYI, it can be reproduced with "c-index-test -std=c++11 -fms-compatibility". llvm-svn: 166261
-
NAKAMURA Takumi authored
llvm-svn: 166257
-
David Blaikie authored
llvm-svn: 166254
-
Nick Lewycky authored
llvm-svn: 166253
-
Douglas Gregor authored
llvm-svn: 166252
-
Douglas Gregor authored
block, so the input files are validated early on, before we've committed to loading the AST file. This (accidentally) fixed a but wherein the main file used to generate the AST file would *not* be validated by the existing validation logic. At the moment, this leads to some duplication of filenames between the source manager block and input-file blocks, as well as validation logic. This will be handled via an upcoming patch. llvm-svn: 166251
-
NAKAMURA Takumi authored
llvm-svn: 166250
-
Argyrios Kyrtzidis authored
This seems to have introduced assertion hit when building compiler-rt. llvm-svn: 166245
-
Eric Christopher authored
llvm-svn: 166240
-
- Oct 18, 2012
-
-
Eli Friedman authored
llvm-svn: 166237
-
Eric Christopher authored
are no known current users of column info. Robustify and fix up a few tests in the process. Reduces the size of debug information by a small amount. Part of PR14106 llvm-svn: 166236
-