Hal Finkel e6a5b33e6e [PowerPC] Adjust load/store costs in PPCTTI ... This provides more realistic costs for the insert/extractelement instructions (which are load/store pairs), accounts for the cheap unaligned Altivec load sequence, and for unaligned VSX load/stores. Bad news: MultiSource/Applications/sgefa/sgefa - 35% slowdown (this will require more investigation) SingleSource/Benchmarks/McGill/queens - 20% slowdown (we no longer vectorize this, but it was a constant store that was scalarized) MultiSource/Benchmarks/FreeBench/pcompress2/pcompress2 - 2% slowdown Good news: SingleSource/Benchmarks/Shootout/ary3 - 54% speedup SingleSource/Benchmarks/Shootout-C++/ary - 40% speedup MultiSource/Benchmarks/Ptrdist/ks/ks - 35% speedup MultiSource/Benchmarks/FreeBench/neural/neural - 30% speedup MultiSource/Benchmarks/TSVC/Symbolics-flt/Symbolics-flt - 20% speedup Unfortunately, estimating the costs of the stack-based scalarization sequences is hard, and adjusting these costs is like a game of whac-a-mole :( I'll revisit this again after we have better codegen for vector extloads and truncstores and unaligned load/stores. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@205658 91177308-0d34-0410-b5e6-96231b3b80d8		2014-04-04 23:51:18 +00:00
..
ARM	When analyzing vectors of element type that require legalization,	2014-03-10 22:59:13 +00:00
ARM64	ARM64: initial backend import	2014-03-29 10:18:08 +00:00
PowerPC	[PowerPC] Adjust load/store costs in PPCTTI	2014-04-04 23:51:18 +00:00
X86	When analyzing vectors of element type that require legalization,	2014-03-10 22:59:13 +00:00
no_info.ll	Make opt grab the triple from the module and use it to initialize the target machine.	2013-01-01 08:00:32 +00:00