| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
block pointer nested inside a block. // rdar:// 9204669
llvm-svn: 128747
|
| |
|
|
|
|
| |
__byref block. // rdar://9204669
llvm-svn: 128726
|
| |
|
|
| |
llvm-svn: 128725
|
| |
|
|
|
|
| |
that of the array element type.
llvm-svn: 128698
|
| |
|
|
|
|
| |
arrays by propagating", it's breaking test in ways I don't understand yet.
llvm-svn: 128693
|
| |
|
|
|
|
|
|
| |
the array alignment to the array access.
- This is more or less the best we can do without having alignment present in
the type system, but is a long way from truly matching how GCC handles this.
llvm-svn: 128691
|
| |
|
|
|
|
| |
__block block declaration. //rdar://9204669
llvm-svn: 128682
|
| |
|
|
|
|
|
|
|
| |
Note this can potentially be enhanced to detect if the __block variable
is actually written by the block, or only when the block "escapes" or
is actually used, but that requires more analysis than it is probably worth
for this simple check.
llvm-svn: 128681
|
| |
|
|
|
|
| |
generate a warning any time the strcpy() function is used with a note suggesting to use a function which provides bounded buffers.
llvm-svn: 128679
|
| |
|
|
|
|
| |
Models mempcpy() so that if length is NULL the destination pointer is returned. Otherwise, the source and destination are confirmed not to be NULL and not overlapping. Finally the copy is validated to not cause a buffer overrun and the return value is bound to the address of the byte after the last byte copied.
llvm-svn: 128677
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
__block object copy/dispose helpers for C++ objects with those for
different variables with completely different semantics simply because
they happen to both be no more aligned than a pointer.
Found by inspection.
Also, internalize most of the helper generation logic within CGBlocks.cpp,
and refactor it to fit my peculiar aesthetic sense.
llvm-svn: 128618
|
| |
|
|
|
|
|
|
| |
wouldn't always be the final node, thus causing the state to continue propagating. Instead,
recover some path-sensitivity by conjuring a symbol.
llvm-svn: 128612
|
| |
|
|
|
|
| |
simulate constructors, but at least the analyzer doesn't think the return value is uninitialized.
llvm-svn: 128611
|
| |
|
|
|
|
| |
- Please never ever ever ever write a tool that sniffs this.
llvm-svn: 128599
|
| |
|
|
|
|
|
|
|
|
|
| |
logic was divorced
from how we process ordinary function calls, had a tremendous about of redundancy, and relied
strictly on inlining behavior (which was incomplete) to provide semantics instead of falling
back to the conservative analysis we use for C functions. This is a significant step into
making C++ analyzer support more useful.
llvm-svn: 128557
|
| |
|
|
|
|
| |
Add a test case for synthesize ivar. // rdar://9070460
llvm-svn: 128554
|
| |
|
|
|
|
| |
for prperty reference types. // rdar://9208606.
llvm-svn: 128551
|
| |
|
|
| |
llvm-svn: 128486
|
| |
|
|
| |
llvm-svn: 128480
|
| |
|
|
|
|
| |
want to stop at closing '}'.
llvm-svn: 128471
|
| |
|
|
| |
llvm-svn: 128459
|
| |
|
|
|
|
|
|
| |
Microsoft mode.
This fixes a bunch of errors when compiling MSVC header files with the -DDLL flag.
llvm-svn: 128457
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
when the resolution took place due to a single template specialization
being named with an explicit template argument list. In this case, the
"resolution" doesn't take into account the target type at all, and
therefore can take place for functions, static member functions, and
*non-static* member functions. The latter weren't being properly checked
and their proper form enforced in this scenario. We now do so.
The result of this last form slipping through was some confusing logic
in IsStandardConversion handling of these resolved address-of
expressions which eventually exploded in an assert. Simplify this logic
a bit and add some more aggressive asserts to catch improperly formed
expressions getting into this routine.
Finally add systematic testing of member functions, both static and
non-static, in the various forms they can take. One of these is
essentially PR9563, and this commit fixes the crash in that PR. However,
the diagnostics for this are still pretty terrible. We at least are now
accepting the correct constructs and rejecting the invalid ones rather
than accepting invalid or crashing as before.
llvm-svn: 128456
|
| |
|
|
|
|
|
|
|
| |
to an assertion failure in the uninitialized variables analysis. The problem is that Sema isn't properly registering a variable in a DeclContext (which -Wuninitialized relies on), but
my expertise on the template instantiation logic isn't good enough to fix this problem for real. This patch worksaround the
problem in -Wuninitialized, but we should fix it for real later.
llvm-svn: 128443
|
| |
|
|
|
|
| |
type-dependent expressions. Fixes rdar://9027658.
llvm-svn: 128437
|
| |
|
|
|
|
|
| |
an executable test to llvm test suite.
// rdar://9070460.
llvm-svn: 128435
|
| |
|
|
|
|
| |
// rdar://9181463
llvm-svn: 128410
|
| |
|
|
| |
llvm-svn: 128401
|
| |
|
|
|
|
| |
to be added... Sorry for the noise.
llvm-svn: 128395
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and flesh out the existing uninitialized testing for field initializers.
The tests come from Richard's original patch, but I've cleaned them up
a bit and ordered them more naturally.
Also, I added a test for the most simple base case:
int x = x;
And it turns out we miss this one! =[ That and another bad FIXME on the
field initializer checking are left in the test.
llvm-svn: 128394
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
required modifying a few tests that specifically use note include stacks
to check the source manager's view of include stacks. I've simply added
the flag to these tests for now, they may have to be more substantially
changed if we decide to remove support for note include stacks
altogether.
Also, add a test for include stacks on notes that was supposed to go in
with the previous commit.
llvm-svn: 128390
|
| |
|
|
|
|
| |
an objc method. Fixes // rdar://9181463
llvm-svn: 128389
|
| |
|
|
|
|
|
|
|
|
|
| |
without the "template" keyword.
For example:
typename C1<T>:: /*template*/ Iterator<0> pos;
Also the error is downgraded to an ExtWarn in Microsoft mode.
llvm-svn: 128387
|
| |
|
|
|
|
| |
AltiVec vector types. It fixes bug 9347.
llvm-svn: 128381
|
| |
|
|
|
|
|
|
|
|
|
| |
This is basically the same idea as the warning on uninitialized uses of
fields within an initializer list. As such, it is on by default and
under -Wuninitialized.
Original patch by Richard Trieu, with some massaging from me on the
wording and grouping of the diagnostics.
llvm-svn: 128376
|
| |
|
|
|
|
| |
PIM section 2.5.1 - after initialization all elements have the value specified by the literal
llvm-svn: 128375
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Emit them instead with the linkage of the VTT.
I'm actually really ambivalent about this; it's what GCC does, but outside
of improving code size (if the linkage is coalescing), I'm not sure it's
at all relevant. Construction vtables are naturally referenced only by the
VTT, which is itself only referenced by complete-object constructors and
destructors; giving the construction vtables possibly-external linkage is
important if you have an optimization that drills through the VTT to a
reference to a particular construction vtable which it cannot just emit
itself.
llvm-svn: 128374
|
| |
|
|
|
|
| |
specifications within the global scope, from Elliot Glaysher.
llvm-svn: 128352
|
| |
|
|
|
|
|
|
| |
returned
from an objective-c message: // rdar://9005189
llvm-svn: 128348
|
| |
|
|
|
|
| |
Fixes rdar://9170766.
llvm-svn: 128346
|
| |
|
|
|
|
| |
with '::', when :: isn't the first part of the selector.
llvm-svn: 128344
|
| |
|
|
| |
llvm-svn: 128343
|
| |
|
|
| |
llvm-svn: 128340
|
| |
|
|
| |
llvm-svn: 128337
|
| |
|
|
|
|
|
|
|
| |
platform implies default visibility. To achieve these, refactor our
lookup of explicit visibility so that we search for both an explicit
VisibilityAttr and an appropriate AvailabilityAttr, favoring the
VisibilityAttr if it is present.
llvm-svn: 128336
|
| |
|
|
| |
llvm-svn: 128334
|
| |
|
|
|
|
|
| |
'unavailable' argument, which specifies that the declaration to which
the attribute appertains is unavailable on that platform.
llvm-svn: 128329
|
| |
|
|
|
|
| |
without a warning.
llvm-svn: 128328
|
| |
|
|
|
|
| |
usually useless, but not always.
llvm-svn: 128326
|
| |
|
|
|
|
|
|
| |
the following '@'. Conceivably, we could skip tokens until something that
can validly start an @interface declaration here, but it's not clear that
it matters.
llvm-svn: 128325
|