lr" instruction cannot be tested just yet. It requires matching a "condition
code", but adding one of those makes things go south quickly...

llvm-svn: 119774

llvm-svn: 119769

llvm-svn: 119768

llvm-svn: 119767

llvm-svn: 119762

llvm-svn: 119761

Fix .o emission of ARM movt/movw. MCSymbolRefExpr::VK_ARM_(HI||LO)16 for the .o path now works for ARM.
Note: lo16AllZero remains in ARMInstrInfo.td - It can be factored out when Thumb movt is repaired.
Existing tests cover this update.

llvm-svn: 119760

llvm-svn: 119755

llvm-svn: 119754

llvm-svn: 119753

Fix bug in DAGCombiner for ARM that was trying to do a ShiftCombine on illegal types (vector should be split first).
Added test case.

llvm-svn: 119749

should delete what when the object gets copied around. It's also making valgrind
upset.

llvm-svn: 119747

llvm-svn: 119744

llvm-svn: 119743

llvm-svn: 119740

This function was being called from two different places for completely
unrelated reasons.  During type legalization, it was called to expand 64-bit
shift operations.  During operation legalization, it was called to handle
Neon vector shifts.  The vector shift code was not written to check for
illegal types, since it was assumed to be only called after type legalization.
Fixed this by splitting off the 64-bit shift expansion into a separate
function.  I don't have a particular testcase for this; I just noticed it
by inspection.

llvm-svn: 119738

llvm-svn: 119737

llvm-svn: 119733

llvm-svn: 119726

Remove movePastCSLoadStoreOps and associated code for simple pointer
increments. Update routines that depended upon other opcodes for save/restore.

Adjust all testcases accordingly.

llvm-svn: 119725

instruction. Any that may be expanded otherwise by MC lowering should
override this value. rdar://8683274

llvm-svn: 119713

  sahf	movl	344(%rdi),%r14d
we used to produce:

t.s:2:1: error: unexpected token in argument list

^

we now produce:
t.s:1:11: error: unexpected token in argument list
sahf	movl	344(%rdi),%r14d
    	    	^

rdar://8581401

llvm-svn: 119676

and testing is easier.  A good example is the unknown-location.ll test that
now can just look for ".loc 1 0 0".  We also don't use a DW_LNE_set_address for
every address change anymore.

llvm-svn: 119613

llvm-svn: 119610

llvm-svn: 119608

the operand to the pattern.

llvm-svn: 119607

llvm-svn: 119604

llvm-svn: 119603

just pretend to be.

llvm-svn: 119602

llvm-svn: 119601

common encoding information.

llvm-svn: 119598

llvm-svn: 119597

llvm-svn: 119593

it as such. Add some encoding information.

llvm-svn: 119588

llvm-svn: 119575

llvm-svn: 119573

This completes the fixes for Radar 8673120.

llvm-svn: 119566

It is generally not sufficient to check if the starting offset is in range
of the maximum offset that can be efficiently used for the target.

llvm-svn: 119565

This makes it more clear that the symbol is an internal, compiler-generated
name and gives a little more description about its contents.

llvm-svn: 119564

It was mistakenly looking at the pointer type when checking for the size of
global variables.  This is a partial fix for Radar 8673120.

llvm-svn: 119563