not in darwin gdb compat mode.

Fixes rdar://10975088

llvm-svn: 162526

TODO: Fix code duplication and coding style.
llvm-svn: 162525

llvm-svn: 162524

 * when checking that a pointer or reference refers to appropriate storage for a type, also check the alignment and perform a null check
 * check that references are bound to appropriate storage
 * check that 'this' has appropriate storage in member accesses and member function calls

llvm-svn: 162523

Hooking up two more calls for the PythonOSPlugin stuff. The part of code to fetch the data and convert it to C++ objects is still missing, but will come

llvm-svn: 162522

llvm-svn: 162521

llvm-svn: 162520

llvm-svn: 162519

llvm-svn: 162518

They were inserted to silence TableGen's warning about
redundant properties. That warning is now gone.

llvm-svn: 162517

Emit TableGen errors if guessInstructionProperties is 0 and
instruction properties can't be inferred from patterns.

Allow explicit instruction properties even when they can be inferred.

This patch doesn't change the TableGen output. Redundant properties
are not yet verified because the tree has errors.

llvm-svn: 162516

llvm-svn: 162515

llvm-svn: 162514

llvm-svn: 162513

llvm-svn: 162512

llvm-svn: 162511

llvm-svn: 162510

generate the Input/Output expressions using Sema::ActOnIdExpression().

llvm-svn: 162509

With inlining, retain count checker starts tracking 'self' through the
init methods. The analyser results were too noisy if the developer
did not follow 'self = [super init]' pattern (which is common
especially in older code bases) - we reported self init anti-pattern AND
possible use-after-free. This patch teaches the retain count
checker to assume that [super init] does not fail when it's not consumed
by another expression. This silences the retain count warning that warns
about possibility of use-after-free when init fails, while preserving
all the other checking on 'self'.

llvm-svn: 162508

use \param and \returns in documentation.

Fixes PR13533.

llvm-svn: 162507

llvm-svn: 162506

Fix undefined behavior (signed integer overflow) when Clang parses a hexfloat with an enormous exponent. Caught by an existing unit test + -ftrapv.

llvm-svn: 162505

llvm-svn: 162504

llvm-svn: 162503

llvm-svn: 162502

This required changing all get() calls to data() and using the simpler constructors.

llvm-svn: 162501

llvm-svn: 162500

llvm-svn: 162499

llvm-svn: 162498

This is how Xcode lets individual files be marked as non-ARC when the rest
of the project is ARC-enabled, so this is necessary for scan-build xcodebuild.

Patch by Paul Eipper!

llvm-svn: 162497

Until we have full support for pointers-to-members, we can at least
approximate some of their use by tracking null and non-null values.
We thus treat &A::m_ptr as a non-null void * symbol, and MemberPointer(0)
as a pointer-sized null constant.

This enables support for what is sometimes called the "safe bool" idiom,
demonstrated in the test case.

llvm-svn: 162495

This is trivial; the UserDefinedConversion always wraps a CXXMemberCallExpr
for the appropriate conversion function, so it's just a matter of
propagating that value to the CastExpr itself.

llvm-svn: 162494

output (we're emitting a specification already and the information
isn't changing) and we're not in old gdb compat mode.

Saves 1% on the debug information for a build of llvm.

Fixes rdar://11043421

llvm-svn: 162493

llvm-svn: 162492

not be set for implicit instantiations, remove the FIXME.  This should be the
last bit for PR13634.  The actual fix happened in r162238.

Motivation: it might be misleading to mark implicit instantiations as
Decl::isImplicit = true.  Because then, in order to be consistent, we should
mark all instantiated members as implicit.  But the user did actually type the
declaration for the member, but the compiler played with it a little bit.

llvm-svn: 162488

turned on and off separate from the platform if you're on darwin.

llvm-svn: 162487

we're using the darwin old gdb compat mode for emitting dwarf.

llvm-svn: 162486

No test case, this is a generalization of r160260.

llvm-svn: 162485

Previously we put a WatchpointSentry object within StopInfo.cpp to disable-and-then-enable the watchpoint itself
while we are performing the actions associated with the triggered watchpoint, which can cause the user-initiated
watchpoint disabling action to be negated.

Add a test case to verify that a watchpoint can be disabled during the callbacks.

llvm-svn: 162483

A first version of a bunch of classes that wrap commonly used Python objects in a ref-counting and type-safe C++ API

llvm-svn: 162481