llvm-6502/test/Transforms/BBVectorize
Hal Finkel 65309660fa Begin incorporating target information into BBVectorize.
This is the first of several steps to incorporate information from the new
TargetTransformInfo infrastructure into BBVectorize. Two things are done here:

 1. Target information is used to determine if it is profitable to fuse two
    instructions. This means that the cost of the vector operation must not
    be more expensive than the cost of the two original operations. Pairs that
    are not profitable are no longer considered (because current cost information
    is incomplete, for intrinsics for example, equal-cost pairs are still
    considered).

 2. The 'cost savings' computed for the profitability check are also used to
    rank the DAGs that represent the potential vectorization plans. Specifically,
    for nodes of non-trivial depth, the cost savings is used as the node
    weight.

The next step will be to incorporate the shuffle costs into the DAG weighting;
this will give the edges of the DAG weights as well. Once that is done, when
target information is available, we should be able to dispense with the
depth heuristic.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@166716 91177308-0d34-0410-b5e6-96231b3b80d8
2012-10-25 21:12:23 +00:00
..
cycle.ll
func-alias.ll
ld1.ll
lit.local.cfg
loop1.ll Begin incorporating target information into BBVectorize. 2012-10-25 21:12:23 +00:00
mem-op-depth.ll
metadata.ll
no-ldstr-conn.ll
req-depth.ll
search-limit.ll
simple3.ll
simple-int.ll
simple-ldstr-ptrs.ll DataLayout should use itself when calculating the size of a vector. 2012-10-21 20:38:03 +00:00
simple-ldstr.ll BBVectorize should ignore unreachable blocks. 2012-10-22 18:00:55 +00:00
simple-sel.ll
simple-tst.ll
simple.ll Begin incorporating target information into BBVectorize. 2012-10-25 21:12:23 +00:00