| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Refine fix to bug 15041. | Bill Schmidt | 2013-02-08 | 1 | -18/+17 |
| | | | | | | | | | | Thanks to help from Nadav and Hal, I have a more reasonable (and even correct!) approach. This specifically penalizes the insertelement and extractelement operations for the performance hit that will occur on PowerPC processors. llvm-svn: 174725 | ||||
| * | Constrain PowerPC autovectorization to fix bug 15041. | Bill Schmidt | 2013-02-07 | 1 | -0/+19 |
| | | | | | | | | | | | | | | Certain vector operations don't vectorize well with the current PowerPC implementation. Element insert/extract performs poorly without VSX support because Altivec requires going through memory. SREM, UREM, and VSELECT all produce bad scalar code. There's a lot of work to do for the cost model before autovectorization will be tuned well, and this is not an attempt to address the larger problem. llvm-svn: 174660 | ||||
| * | Remove unused variables, silences -Wunused-variable | Dmitri Gribenko | 2013-01-25 | 1 | -4/+2 |
| | | | | | llvm-svn: 173526 | ||||
| * | Initial implementation of PPCTargetTransformInfo | Hal Finkel | 2013-01-25 | 1 | -0/+220 |
| This provides a place to add customized operation cost information and control some other target-specific IR-level transformations. The only non-trivial logic in this checkin assigns a higher cost to unaligned loads and stores (covered by the included test case). llvm-svn: 173520 | |||||

