- Jan 24, 2012
-
-
David Blaikie authored
llvm-svn: 148774
-
Argyrios Kyrtzidis authored
llvm-svn: 148772
-
Chandler Carruth authored
the tests are making assertions about the name of the clang binary, so we should ensure that the name is as stable as possible. llvm-svn: 148767
-
Argyrios Kyrtzidis authored
llvm-svn: 148765
-
Fariborz Jahanian authored
matches a typedef declaring an object type. // rdar://10733000 llvm-svn: 148760
-
Akira Hatanaka authored
type of pointers. llvm-svn: 148753
-
Fariborz Jahanian authored
its line. // rdar://10711037 llvm-svn: 148747
-
Akira Hatanaka authored
llvm-svn: 148744
-
- Jan 23, 2012
-
-
Bill Wendling authored
llvm-svn: 148739
-
Sebastian Redl authored
Fix some review comments. Add a test for deduction when std::initializer_list isn't available yet. Fix redundant error messages. This fixes and outstanding FIXME too. llvm-svn: 148735
-
Argyrios Kyrtzidis authored
@implementation I(cat) suppress subsequent references to 'I'. rdar://10568103 llvm-svn: 148730
-
Argyrios Kyrtzidis authored
Sema::DiagnoseSentinelCalls() does. llvm-svn: 148722
-
Kaelyn Uhrain authored
Previously, for unqualified lookups, a positive cache hit is used as the only non-keyword correction and a negative cache hit immediately returns an empty TypoCorrection. With the new callback objects, this behavior causes false negatives by not accounting for the fact that callback objects alter the set of potential/allowed corrections. The new behavior is to seed the set of corrections with the cached correction (for positive hits) to estabilishing a baseline edit distance. Negative cache hits are only stored or used when either no callback object is provided or when it returns true for a call to ValidateCandidate with an empty TypoCorrection (i.e. when ValidateCandidate does not seem to be doing any checking of the TypoCorrection, such as when an instance of the base callback class is used solely to specify the set of keywords to be accepted). llvm-svn: 148720
-
Kostya Serebryany authored
llvm-svn: 148716
-
-
Argyrios Kyrtzidis authored
without C++-specific features. Use it to set the language to C++ when indexing non-C-like structs. rdar://10732579 llvm-svn: 148708
-
-
-
-
Argyrios Kyrtzidis authored
of macro arguments. For "MAC1( MAC2(foo) )" and location of 'foo' token it would return "MAC1" instead of "MAC2". llvm-svn: 148704
-
Douglas Gregor authored
expression) when code-completing member access expressions. Fixes <rdar://problem/10717172>. llvm-svn: 148703
-
Douglas Gregor authored
compatibility. llvm-svn: 148702
-
Douglas Gregor authored
to an error, so that users can turn them off if necessary. Note that this does *not* change the behavior of in a SFINAE context, where we still flag an error even if the warning is disabled. This matches GCC's behavior. llvm-svn: 148701
-
Nick Lewycky authored
X86 backend in LLVM. llvm-svn: 148689
-
Nico Weber authored
llvm-svn: 148683
-
Nico Weber authored
This matches cl.exe's behavior and fixes PR11791. llvm-svn: 148682
-
David Blaikie authored
This is for consistency, since the flag is actually under -Wswitch now, rather than -Wswitch-enum (since it's really valuable for the former and rather orthogonal to the latter) llvm-svn: 148680
-
David Blaikie authored
Clang previously implemented -Wswitch-enum the same as -Wswitch. This patch corrects the behavior to match GCC's. The critical/only difference being that -Wswitch-enum is not silenced by the presence of a default case in the switch. llvm-svn: 148679
-
Nico Weber authored
No other changes. llvm-svn: 148678
-
Nico Weber authored
Also change a || that I accidentally changed to && back to ||. llvm-svn: 148677
-
Nico Weber authored
MSVC2010's pair class has a move assignment operator but no explicit copy constructor, which makes it unusable without this change. For symmetry, let move copy constructors not mark the default assignment operator as deleted either. Both changes match cl.exe's behavior. Fixes pr11826. Also update the standard excerpt to point to the right paragraph. llvm-svn: 148675
-
Eli Friedman authored
llvm-svn: 148673
-
- Jan 22, 2012
-
-
David Blaikie authored
For consistency with GCC & reasonable sanity. The FIXME suggests that the original author was perhaps using the default check for some other purpose, not realizing the more obvious limitation/false-negatives it creates, but this doesn't seem to produce any regressions & fixes the included test. llvm-svn: 148649
-
David Blaikie authored
This matches GCC's documented (& actual) behavior. What Clang had implemented as -Wswitch-enum was actually GCC's -Wswitch behavior. -Wswitch is on by default (part of -Wall) and warns if a switch-over-enum, without a default case, covers all enum values. -Wswitch-enum, on the other hand, does not have the default clause and should fire even in the presence of a default. This warning is off by default. With this change the -Wswitch-enum flag is off-by-default in Clang but has no functionality at the moment. I'll add that in a future commit. llvm-svn: 148648
-
Francois Pichet authored
In Microsoft Mode, disable the C++11 strict integral conversion rules for enumerator that were introduced with r148439. Otherwise MSVC headers won't compile in C++ 11 mode. llvm-svn: 148642
-
- Jan 21, 2012
-
-
David Blaikie authored
This warning acts as the complement to the main -Wswitch-enum warning (which warns whenever a switch over enum without a default doesn't cover all values of the enum) & has been an an-doc coding convention in LLVM and Clang in my experience. The purpose is to ensure there's never a "dead" default in a switch-over-enum because this would hide future -Wswitch-enum errors. The name warning has a separate flag name so it can be disabled but it's grouped under -Wswitch-enum & is on-by-default because of this. The existing violations of this rule in test cases have had the warning disabled & I've added a specific test for the new behavior (many negative cases already exist in the same test file - and none regressed - so I didn't add more). Reviewed by Ted Kremenek ( http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20120116/051690.html ) llvm-svn: 148640
-
NAKAMURA Takumi authored
llvm-svn: 148637
-
NAKAMURA Takumi authored
llvm-svn: 148636
-
Anna Zaks authored
[analyzer] It's possible to have a non PointerType expression evaluate to a Loc value. When this happens, use the default type. llvm-svn: 148631
-
Bob Wilson authored
llvm-svn: 148630
-