| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
This time, make sure we don't try to print fixits with newline characters,
since they don't have a valid column width, and they don't look good anyway.
PR13417 (and originally <rdar://problem/11877454>)
llvm-svn: 160561
|
| |
|
|
|
|
| |
rdar://11842763
llvm-svn: 160554
|
| |
|
|
|
|
|
|
| |
of c-functions nested in namespace in method implementations
by turning off its delayed parsing until a proper solution is
figured out. pr13418
llvm-svn: 160552
|
| |
|
|
|
|
| |
paragraph.
llvm-svn: 160550
|
| |
|
|
| |
llvm-svn: 160542
|
| |
|
|
|
|
|
|
| |
nullptr.
Fixes PR13413, -Wunused-private-field now warns on unused fields initialized to NULL.
llvm-svn: 160541
|
| |
|
|
|
|
| |
make it match the flag it tests.
llvm-svn: 160536
|
| |
|
|
|
|
|
|
| |
FileCheck.
This avoids copying files around needlessly during test runs.
llvm-svn: 160535
|
| |
|
|
|
|
| |
clients to default text files to 'eol-native'.
llvm-svn: 160534
|
| |
|
|
| |
llvm-svn: 160528
|
| |
|
|
|
|
|
|
| |
or implementation since we've now got a different layout.
Fixes rdar://11842763
llvm-svn: 160526
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
While we still want to consider this a hard error (non-POD variadic args are
normally a DefaultError warning), delaying the diagnostic allows us to give
better error messages, which also match the usual non-POD errors more closely.
In addition, this change improves the diagnostic messages for format string
argument type mismatches by passing down the type of the callee, so we can
say "variadic method" or "variadic function" appropriately.
<rdar://problem/11825593>
llvm-svn: 160517
|
| |
|
|
|
|
| |
No functionality change.
llvm-svn: 160516
|
| |
|
|
|
|
|
|
|
| |
Previously, we would ask for the SourceLocation of an argument even if
it were NULL (i.e. if Sema resulted in an ExprError trying to build it).
<rdar://problem/11890818>
llvm-svn: 160515
|
| |
|
|
|
|
| |
Makes sure we don't overflow the stack.
llvm-svn: 160511
|
| |
|
|
|
|
|
| |
This macro was being unconditionally set to zero, preceded by a FIXME comment.
This fixes <rdar://problem/11845441>. Patch by Michael Gottesman!
llvm-svn: 160491
|
| |
|
|
|
|
| |
longer emit a diagnostic when the enumeration's name matches that of the class. Fixes PR13128.
llvm-svn: 160490
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The hack of recognizing a -D__IPHONE_OS_VERSION_MIN_REQUIRED option
in place of -mios-simulator-version-min leaves the Darwin version
unspecified. It can be set separately with -mmacosx-version-min (which
makes no sense) or inferred to match the host version (which is unpredictable
and usually wrong). This really needs to get cleaned up, but in the
meantime, force the OS X version to 10.6 so that the behavior is sane for
the iOS simulator. Thanks for Argyrios for the patch.
<rdar://problem/11858187>
llvm-svn: 160484
|
| |
|
|
|
|
|
| |
TextComment node was considered whitespace even if it contained other child
nodes.
llvm-svn: 160474
|
| |
|
|
|
|
| |
it solves them).
llvm-svn: 160462
|
| |
|
|
|
|
|
|
|
|
|
|
| |
As pointed out by Anna, we only differentiate between explicit message sends
This also adds support for ObjCSubscriptExprs, which are basically the same
as properties in many ways. We were already checking these, but not emitting
nice messages for them.
This depends on the llvm::PointerIntPair change in r160456.
llvm-svn: 160461
|
| |
|
|
| |
llvm-svn: 160455
|
| |
|
|
|
|
|
|
|
|
| |
references
(in uses of dynamic_cast<>).
Fixes <rdar://problem/11817693>.
llvm-svn: 160427
|
| |
|
|
|
|
| |
types. Fixes crash in <rdar://problem/11671507>.
llvm-svn: 160424
|
| |
|
|
|
|
|
|
| |
be defined as deleted, take cv-qualifiers on class members into account when
looking up the copy or move constructor or assignment operator which will be
used for them.
llvm-svn: 160418
|
| |
|
|
|
|
|
| |
constructor will be used for moving that object, in the computation of its
exception specification.
llvm-svn: 160417
|
| |
|
|
|
|
|
|
|
|
|
| |
and a function template instantiation, if there's a parameter pack in the
declaration and one at the same place in the instantiation, don't assume that
the pack wasn't expanded -- it may have expanded to nothing. Instead, go ahead
and check whether the parameter pack was expandable. We can do this as a
side-effect of the work we'd need to do anyway, to find how many parameters
were produced.
llvm-svn: 160416
|
| |
|
|
| |
llvm-svn: 160415
|
| |
|
|
|
|
|
|
| |
[temp.deduct.call]p4 under Objective-C++ ARC, make sure to adjust the
qualifiers to introduce the implicit strong lifetime when
needed. Fixes <rdar://problem/11825671>.
llvm-svn: 160412
|
| |
|
|
|
|
| |
completions. Fixes <rdar://problem/11889572>.
llvm-svn: 160407
|
| |
|
|
|
|
| |
can be found with quoted strings instead. Implements PR13201.
llvm-svn: 160406
|
| |
|
|
| |
llvm-svn: 160399
|
| |
|
|
|
|
| |
constant evaluation. <rdar://problem/11874571>.
llvm-svn: 160394
|
| |
|
|
|
|
| |
Fixes pr13353.cpp.
llvm-svn: 160393
|
| |
|
|
|
|
| |
Patch by Eli Bendersky.
llvm-svn: 160385
|
| |
|
|
| |
llvm-svn: 160383
|
| |
|
|
|
|
|
| |
Due to performance cost, this is an opt-in option placed
under -Wassign-enum. // rdar://11824807
llvm-svn: 160382
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Checks against nil often appear as guards in macros, and comparing
Objective-C literals to nil has well-defined behavior (if tautological).
On OS X, 'nil' has not been typed as 'id' since 10.6 (possibly earlier),
so the warning was already not firing, but other runtimes continue to use
((id)0) or some variant. This change accepts comparisons to any null pointer;
to keep it simple, it looks through all casts (not just casts to 'id').
PR13276
llvm-svn: 160379
|
| |
|
|
|
|
|
|
|
| |
Suggested by Ted, since string literal comparison is at least slightly more
sensible than comparison of runtime literals. (Ambiguous language on
developer.apple.com implies that strings are guaranteed to be uniqued within
a translation unit and possibly across a linked binary.)
llvm-svn: 160378
|
| |
|
|
|
|
|
|
| |
Recovering as if the user had actually called -isEqual: is a bit too far from
the semantics of the program as written, /even though/ it's probably what they
intended.
llvm-svn: 160377
|
| |
|
|
|
|
|
| |
is a bit fuzzy, but matches gcc behavior and existing code bases seem to
depend on it.
llvm-svn: 160364
|
| |
|
|
|
|
| |
also with gnuwin32.
llvm-svn: 160362
|
| |
|
|
| |
llvm-svn: 160353
|
| |
|
|
|
|
|
|
|
|
|
| |
- lib/Driver/Driver.cpp, tools/driver/driver.cpp: Exit status should not be propagated, although clang driver should catch exceptions.
- test/Driver/crash-report.c: Add REQUIRES:shell for now.
FIXME: setenv should work also on Lit.InternalShellRunner.
- test/Driver/crash-report.c: Remove XFAIL.
Thanks to Chad, To point out the issue.
llvm-svn: 160343
|
| |
|
|
|
|
| |
Set all of $TMPDIR, $TEMP and $TMP, or a certain host might set $TEMP.
llvm-svn: 160342
|
| |
|
|
|
|
| |
to build a type before seeing the definition.
llvm-svn: 160339
|
| |
|
|
|
|
|
| |
* Treat compound assignment as a use, at Jordy's request.
* Always add compound assignments into the CFG, so we can correctly diagnose the use in 'return x += 1;'
llvm-svn: 160334
|
| |
|
|
| |
llvm-svn: 160332
|
| |
|
|
|
|
|
|
|
|
| |
use out of TransferFunctions, and compute it in advance rather than on-the-fly.
This allows us to handle compound assignments with DeclRefExprs on the RHS
correctly, and also makes it trivial to treat const& function parameters as not
initializing the argument. The patch also makes both of those changes.
llvm-svn: 160330
|
| |
|
|
|
|
| |
<rdar://problem/11818967>
llvm-svn: 160328
|