llvm-svn: 130568

llvm-svn: 130567

simulator wants to use it.

llvm-svn: 130566

interface.

Added a quick way to set the platform though the SBDebugger interface. I will
actually an a SBPlatform support soon, but for now this will do.

ConnectionFileDescriptor can be passed a url formatted as: "fd://<fd>" where
<fd> is a file descriptor in the current process. This is handy if you have
services, deamons, or other tools that can spawn processes and give you a
file handle.

llvm-svn: 130565

llvm-svn: 130564

llvm-svn: 130562

llvm-svn: 130561

Make FastEmit_ri_ try a bit harder to succeed for supported operations; FastEmit_i can fail for non-Thumb2 ARM.  Makes ARMSimplifyAddress work correctly, and reduces the number of fast-isel bailouts on non-Thumb ARM.

llvm-svn: 130560

Adjust test/Analysis/retain-release.m to also test the retain/release checker in Objective-C++ mode.

llvm-svn: 130559

llvm-svn: 130558

llvm-svn: 130557

emulate instruction classes.

llvm-svn: 130556

Radar 9333566.  Patch by Chad Rosier!

llvm-svn: 130554

llvm-svn: 130552

llvm-svn: 130551

llvm-svn: 130550

if it ever did it needs the def machinery.

llvm-svn: 130549

Filter out pattterns from the FastISel emitter which it doesn't actually know how to handle.  No significant functionality change at the moment, but it's necessary for some changes I'm planning.

llvm-svn: 130547

llvm-svn: 130546

rhs when its 'forwarding' pointer may be modified 
in rhs evaluation as result of call to Block_copy.
// rdar://9309454

llvm-svn: 130545

lets this code be used when producing assembly code for old assemblers without
uleb support.

llvm-svn: 130544

llvm-svn: 130543

llvm-svn: 130542

llvm-svn: 130541

llvm-svn: 130540

Fix a rather obscure crash caused by ARM fast-isel generating code which redefines a register.
rdar://problem/9338332 .

llvm-svn: 130539

positives still further.

The plan is to:

1) Create a more targeted warning for memset of memory pointing at
   a type with virtual methods or bases where a vptr would be
   overwritten.
2) Consider turning the above warning back on by default.
3) Evaluate whether any false positives in the existing warning can be
   detected and white listed in the warning implementation.
4) If #3 lowers the noise floor enough, enable the full warning in -Wall
   or -Wextra.

Comments or suggestions welcome. Even more welcome are specific test
cases which trigger the warning and shouldn't.

llvm-svn: 130538

llvm-svn: 130536

Change -Wparentheses to not imply -Widiomatic-parentheses.  Users rarely want to see these warnings, and often explicitly pass -Wparentheses.

llvm-svn: 130535

for bools, but is a start.

llvm-svn: 130534

llvm-svn: 130533

restored after parsing "SBTarget".  Indentation matters in Python. :-)

llvm-svn: 130532

the breakpoint ID and provides the semantics needed for '==' and '!='.  And
modify LLDBIteratorTestCase.lldb_iter_2() to use '==' between two SBBreakpoint's.

llvm-svn: 130531

issue.

llvm-svn: 130530

llvm-svn: 130529

llvm-svn: 130528

llvm-svn: 130527

llvm-svn: 130526

llvm-svn: 130525

currently used, because variables don't get reported as being "defined".

llvm-svn: 130524