llvm-svn: 78850

llvm-svn: 78848

llvm-svn: 78835

llvm-svn: 78829

Enhance the InstrStage object to enable the specification of an Itinerary with overlapping stages. The default is to maintain the current behavior that the "next" stage immediately follows the previous one.

llvm-svn: 78827

llvm-svn: 78817

leaving the mayLoad and mayStore settings around only the load/store
instructions where those can't be inferred from the patterns.

llvm-svn: 78815

llvm-svn: 78806

pair instead of from a virtual method on TargetMachine.  This cuts the final
ties of TargetAsmInfo to TargetMachine, meaning that MC can now use 
TargetAsmInfo.

llvm-svn: 78802

llvm-svn: 78790

llvm-svn: 78779

llvm-svn: 78778

llvm-svn: 78777

llvm-svn: 78776

Set "mayLoad" and "mayStore" on the load/store instructions.

llvm-svn: 78761

llvm-svn: 78745

"inlineasmstart/end" strings so that the contents of the directive
are separate from the comment character.  This lets elf targets
get #APP/#NOAPP for free even if they don't use "#" as the comment
character.  This also allows hoisting the darwin stuff up to the
shared TAI class.

llvm-svn: 78737

llvm-svn: 78736

darwin/arm support for .no_dead_strip

llvm-svn: 78734

llvm-svn: 78732

llvm-svn: 78730

llvm-svn: 78729

template in PPC backend for TAI.

llvm-svn: 78727

llvm-svn: 78717

the latter is capable of representing either a primitive or an extended type.

llvm-svn: 78713

LLVMTargetMachine ctor.  It is currently unused.

llvm-svn: 78711

version.  This allows TAI implementations to specify the directive to use
based on the mode being codegen'd for.

The real fix for this is to remove JumpTableDirective, but I don't feel
like diving into the jumptable snarl just now.

llvm-svn: 78709

llvm-svn: 78701

llvm-svn: 78683

llvm-svn: 78678

llvm-svn: 78666

llvm-svn: 78665

llvm-svn: 78659

match base only address, i.e. [r] since Thumb2 requires a offset register field.
For those, use [r + imm12] where the immediate is zero.
Note the generated assembly code does not look any different after the patch.
But the bug would have broken the JIT (if there is Thumb2 support) and it can
break later passes which expect the address mode to be well-formed.

llvm-svn: 78658

llvm-svn: 78657

llvm-svn: 78655

llvm-svn: 78654

the overloaded vector types allowed floating-point or integer vector elements.
Most of these operations actually depend on the element type, so bitcasting
was not an option.

If you include the vpadd intrinsics that I updated earlier, this gets rid
of 20 intrinsics.

llvm-svn: 78646

llvm-svn: 78632

llvm-svn: 78629