summaryrefslogtreecommitdiffstats
path: root/libcxx
diff options
context:
space:
mode:
authorHal Finkel <hfinkel@anl.gov>2016-03-31 02:56:05 +0000
committerHal Finkel <hfinkel@anl.gov>2016-03-31 02:56:05 +0000
commit851b33a0b1e3c0377f7f8f6262e9ce6a711de235 (patch)
tree40bb9aab0ad5ea295c04d8de1b26200c57bbdbc6 /libcxx
parent8ed5cac97c1c7876fcde080bd58ee4969347a8a7 (diff)
downloadbcm5719-llvm-851b33a0b1e3c0377f7f8f6262e9ce6a711de235.tar.gz
bcm5719-llvm-851b33a0b1e3c0377f7f8f6262e9ce6a711de235.zip
[PowerPC] Load two floats directly instead of using one 64-bit integer load
When dealing with complex<float>, and similar structures with two single-precision floating-point numbers, especially when such things are being passed around by value, we'll sometimes end up loading both float values by extracting them from one 64-bit integer load. It looks like this: t13: i64,ch = load<LD8[%ref.tmp]> t0, t6, undef:i64 t16: i64 = srl t13, Constant:i32<32> t17: i32 = truncate t16 t18: f32 = bitcast t17 t19: i32 = truncate t13 t20: f32 = bitcast t19 The problem, especially before the P8 where those bitcasts aren't legal (and get expanded via the stack), is that it would have been better to use two floating-point loads directly. Here we add a target-specific DAGCombine to do just that. In short, we turn: ld 3, 0(5) stw 3, -8(1) rldicl 3, 3, 32, 32 stw 3, -4(1) lfs 3, -4(1) lfs 0, -8(1) into: lfs 3, 4(5) lfs 0, 0(5) llvm-svn: 264988
Diffstat (limited to 'libcxx')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud