Don't form an out of bounds pointer just to test if it
would be out of bounds.

Also perform the same bounds checking for all the previous
mapped structures.

llvm-svn: 149750

Now this works with and without --with-clang-srcdir, with and
without an out-of-tree build.

llvm-svn: 149749

Sync with the change in r149652.

Also fix the comment to sync with LLVM's config.h header.

llvm-svn: 149748

 - osx.coreFoundation.containers.IndexOutOfBounds
 - osx.cocoa.SelfInit

llvm-svn: 149747

llvm-svn: 149746

(Also renames in other ObjC checkers to create one category of checks.)

llvm-svn: 149745

last commit.  Sorry for the outage.

llvm-svn: 149744

instead of the __repr__. __repr__ is a function that should return an
expression that can be used to recreate an python object and we were using
it to just return a human readable string.

Fixed a crasher when using the new implementation of SBValue::Cast(SBType).

Thread hardened lldb::SBValue and lldb::SBWatchpoint and did other general
improvements to the API.

Fixed a crasher in lldb::SBValue::GetChildMemberWithName() where we didn't
correctly handle not having a target.

llvm-svn: 149743

llvm-svn: 149742

llvm-svn: 149741

by adding a triple, and the typedef makes things worse on windows.

llvm-svn: 149740

of ArrayRef goodness. No functionality change.

llvm-svn: 149739

llvm-svn: 149738

llvm-svn: 149737

llvm-svn: 149736

want to provide "po"-like functionality which
treats the result of an expression implicitly as
"id" (if it is not otherwise known) and prints
it as an Objective-C object.

This has in the past been gated by the
"DebuggerSupport" language option, but that is
too general.  Debuggers also provide other commands
like "print" that do not make any assumptions
about whether the object is an Objective-C object.

This patch makes the assumption conditional on a
new language option: DebuggerCastResultToId.  I
have also made corresponding modifications to the
testsuite.

llvm-svn: 149735

llvm-svn: 149734

declaration is a reference. rdar://10749990

llvm-svn: 149733

llvm-svn: 149732

Suppress the used-but-not-defined warning for static data members while I look into a rather nasty bug in the new odr-use marking code.

llvm-svn: 149731

llvm-svn: 149730

  The recent support for potential constant expressions exposed a bug in the
  implementation of libstdc++4.6, where numeric_limits<int>::min() is defined
  as (int)1 << 31, which isn't a constant expression. Disable the 'constexpr
  function never produces a constant expression' error inside system headers
  to compensate.

llvm-svn: 149729

llvm-svn: 149728

They are not used any more. Simply use SlotIndex() to get an invalid
index.

llvm-svn: 149727

llvm-svn: 149726

llvm-svn: 149725

llvm-svn: 149724

llvm-svn: 149723

llvm-svn: 149722

Idea by Jean-Daniel Dupas.

llvm-svn: 149721

Remove __attribute__((weak)) on function prototype.  It has a different meaning on prototypes then it does on definitions.  It is not needed on the prototype and causes build failures for static codegen

llvm-svn: 149720

llvm-svn: 149719

Still left: explicit captures in lambdas need to cause implicit capture, and I need to take a look at the diagnostics for some cases.

llvm-svn: 149718

llvm-svn: 149717

llvm-svn: 149716

Calls that use register mask operands don't have implicit defs for
returned values.  The register mask operand handles the call clobber,
but it always behaves like a set of dead defs.

Add live implicit defs for any implicitly defined physregs that are
actually used.

llvm-svn: 149715

llvm-svn: 149714

When adding the {-1, -1} entry to the DFAStateInputTable, we
need to increment the index used to populate the DFAStateEntryTable.
Otherwise, the entry table will be off by one for each transition
after the {-1, -1} entry. PR11908.

llvm-svn: 149713

llvm-svn: 149712

__gxx_personality_v0 and __cxa_call_unexpected are complete on darwin and I *think* linux (not positive), but still unimplemented on arm.

llvm-svn: 149711