error in foo.o; no .eh_frame_hdr table will be created.

llvm-svn: 129635

boundary.  <rdar://problem/8933028>

llvm-svn: 129634

Fix divmod libcall lowering. Convert to {S|U}DIVREM first and then expand the node to a libcall. rdar://9280991

llvm-svn: 129633

llvm-svn: 129632

Break the arc-profile code out to a function like the notes emission code is,
and reorder the functions in the file.

The only functionality change is that we no longer modify the Module when the
Module has no debug info to use.

llvm-svn: 129631

does. Also mostly implement it. Still a work-in-progress, but generates legal
output on crafted test cases.

llvm-svn: 129630

llvm-svn: 129629

Introduce Rewriter::IncreaseIndentation() which increase indentations for the lines between the given source range.
To determine what the indentation should be, a SourceLocation 'parentIndent' parameter is used that should be at
a source location with an indentation one degree lower than the given range.

llvm-svn: 129628

llvm-svn: 129627

llvm-svn: 129626

llvm-svn: 129625

Introduce support to encode Objective-C property information in debugging information generated for an interface.

llvm-svn: 129624

Add support for "dynamic values" for C++ classes.  This currently only works for "frame var" and for the
expressions that are simple enough to get passed to the "frame var" underpinnings.  The parser code will
have to be changed to also query for the dynamic types & offsets as it is looking up variables.

The behavior of "frame var" is controlled in two ways.  You can pass "-d {true/false} to the frame var
command to get the dynamic or static value of the variables you are printing.

There's also a general setting:

target.prefer-dynamic-value (boolean) = 'true'

which is consulted if you call "frame var" without supplying a value for the -d option.

llvm-svn: 129623

llvm-svn: 129621

llvm-svn: 129620

rdar://problem/9292717

llvm-svn: 129619

The a bit must be encoded as 0.

rdar://problem/9292625

llvm-svn: 129618

Add test case.

llvm-svn: 129617

llvm-svn: 129616

// rdar://9287695

llvm-svn: 129615

llvm-svn: 129614

llvm-svn: 129613

llvm-svn: 129612

which advances when src collides with a purged slot.
Hi Stephen, you're welcome to overwrite/or improve upon this version.  Thanks.

llvm-svn: 129611

a case involving EOR, so I only added a test for ORR.

llvm-svn: 129610

llvm-svn: 129609

llvm-svn: 129608

llvm-svn: 129607

Fix lines that have incorrect indentation or exceed 80 columns. There is no change in functionality.

llvm-svn: 129606

Stephen Wilson is working on a better performing patch in the meantime.

llvm-svn: 129605

Objective-C pointer to void* as a "conversion to void*". This allows
us to prefer an Objective-C object pointer conversion to a superclass
object pointer over an Objective-C object pointer conversion to
cv-void*. Fixes PR9735.

llvm-svn: 129603

problem as all of the other instructions we fold with CMPs.

llvm-svn: 129602

llvm-svn: 129601

llvm-svn: 129600

fixes <rdar://problem/9287901>.

llvm-svn: 129599

DWARFDebugAranges::Sort() calls std::stable_sort() over a set of address ranges
and then proceeds to collapse neighboring ranges together.

One problem with the current implementation is that it does an incomplete job.
When a pair of ranges are merged the next pair considered does not include the
just-merged range.  IOW, three consecutive ranges are never collapsed into one.

Another problem is that for each range merged we are calling
std::vector::erase() which "shifts" all remaining elements of the vector by one
position on every merge.  The end result (in the worst case) is a quadratic
algorithm -- not good when the input vector is large.

The following patch merges all consecutive ranges and removes the quadratic
behavior.  The implementation uses an auxiliary vector of indices in order to
remember all ranges that can be dropped, then performs the coalescing of ranges
in a single pass.

Patch from Stephen Wilson with some minor modification by me.

llvm-svn: 129595

Add pass that expands pseudo instructions into target instructions after register allocation. Define pseudos that get expanded into mtc1 or mfc1 instructions.

llvm-svn: 129594

address space. I could see that this functionality would be useful,
but not in its current form (where the address space is ignored):
rather, we'd want to encode the address space into the parameter list
passed to operator new/operator delete somehow, which would require a
bunch more semantic analysis.

llvm-svn: 129593

"new" expression. This matches GCC's parser. Test is forthcoming.

llvm-svn: 129592

Increase SubtargetFeatureKV Value and Implies fields to 64 bits since some targets are getting very close to 32 subtarget features. Also teach tablegen to error when there are more than 64 features to guard against undefined behavior. rdar://9282332

llvm-svn: 129590