using two instructions (sethi and store).

llvm-svn: 183090

llvm-svn: 183088

Reviewers: Bigcheese

CC: llvm-commits

Differential Revision: http://llvm-reviews.chandlerc.com/D905

llvm-svn: 183087

llvm-svn: 183086

llvm-svn: 183083

llvm-svn: 183081

index greater than the size of the vector is invalid. The shuffle may be
shrinking the size of the vector. Fixes a crash!

Also drop the maximum recursion depth of the safety check for this
optimization to five.

llvm-svn: 183080

llvm-svn: 183079

llvm-svn: 183078

Also simplify code a bit while there. No functionality change.

llvm-svn: 183076

No functionality change.

llvm-svn: 183075

llvm-svn: 183074

llvm-svn: 183073

llvm-svn: 183072

llvm-svn: 183071

Very sorry, it was committed from the wrong branch by mistake.

llvm-svn: 183070

llvm-svn: 183069

The MOV64ri64i32 instruction required hacky MCInst lowering because it
was allocated as setting a GR64, but the eventual instruction ("movl")
only set a GR32. This converts it into a so-called "MOV32ri64" which
still accepts a (appropriate) 64-bit immediate but defines a GR32.
This is then converted to the full GR64 by a SUBREG_TO_REG operation,
thus keeping everyone happy.

This fixes a typo in the opcode field of the original patch, which
should make the legact JIT work again (& adds test for that problem).

llvm-svn: 183068

llvm-svn: 183067

Removed a comment above an include which is unnecessary and added a missing closing @} for a doxygen comment.

llvm-svn: 183065

llvm-svn: 183064

Also added a few more method comments and performed some copy editing.

llvm-svn: 183063

This also makes TableGen able to compute sizes/offsets of synthesized
indices representing tuples.

llvm-svn: 183061

Fixes rdar:14036816, PR16130.

There is an opportunity to compute precise trip counts for 'or'
expressions and multi-exit loops.
rdar:14038809: Optimize trip count computation for multi-exit loops.

To do this we need to record the fact that ExitLimit assumes NSW. When
it does not we can safely assume that the loop trip count is the
minimum ExitLimt across all subexpressions and loop exits.

llvm-svn: 183060

seems to have caused PR16192 and other JIT related failures.

llvm-svn: 183059

llvm-svn: 183057

llvm-svn: 183054

llvm-svn: 183053

llvm-svn: 183052

llvm-svn: 183051

Use ScalarEvolution's getBackedgeTakenCount API instead of getExitCount since
that is really what we want to know. Using the more specific getExitCount was
safe because we made sure that there is only one exiting block.

No functionality change.

llvm-svn: 183047

Account for the cost of scaling factor in Loop Strength Reduce when rating the
formulae. This uses a target hook.

The default implementation of the hook is: if the addressing mode is legal, the
scaling factor is free.

<rdar://problem/13806271>

llvm-svn: 183045

llvm-svn: 183043

llvm-svn: 183042

llvm-svn: 183041

llvm-svn: 183040

We check that instructions in the loop don't have outside users (except if
they are reduction values). Unfortunately, we skipped this check for
if-convertable PHIs.

Fixes PR16184.

llvm-svn: 183035

Fixes a leak found by valgrind.

llvm-svn: 183031

llvm-svn: 183028

Namely, check if the target allows to fold more that one register in the
addressing mode and if yes, adjust the cost accordingly.

Prior to this commit, reg1 + scale * reg2 accesses were artificially preferred
to reg1 + reg2 accesses. Indeed, the cost model wrongly assumed that reg1 + reg2
needs a temporary register for the computation, whereas it was correctly
estimated for reg1 + scale * reg2.

<rdar://problem/13973908>

llvm-svn: 183021