aboutsummaryrefslogtreecommitdiff
path: root/gcc/tree-vrp.c
diff options
context:
space:
mode:
authorSegher Boessenkool <segher@kernel.crashing.org>2016-10-18 10:00:00 +0200
committerSegher Boessenkool <segher@gcc.gnu.org>2016-10-18 10:00:00 +0200
commit8f784f6bde1ff14f73bc8337e5f250209a6831d8 (patch)
tree2c28aa3372658183b6f063cf897d857331cb97ef /gcc/tree-vrp.c
parent62869a1ca1ddb89e9cb5c808bfe678979e4090f0 (diff)
downloadgcc-8f784f6bde1ff14f73bc8337e5f250209a6831d8.zip
gcc-8f784f6bde1ff14f73bc8337e5f250209a6831d8.tar.gz
gcc-8f784f6bde1ff14f73bc8337e5f250209a6831d8.tar.bz2
rs6000: Fix separate shrink-wrapping for TARGET_MULTIPLE
We cannot use {SAVE,REST}_MULTIPLE and separate shrink-wrapping together, not without checking when actually emitting the prologue/epilogue that the registers to save/restore are actually still one contiguous block up to (and including) 31. So either: 1) We delay the decision of whether to use lmw/stmw to later; 2) We disallow shrink-wrapping separate (integer) components when those strategies are selected; or 3) We don't use those strategies if we use separate shrink-wrapping. This patch does 3). In the long term it may be best to do 1) instead, it can be slightly more efficient. This caused problems on darwin (it is the only config that uses lmw/stmw instructions by default). * config/rs6000/rs6000.c (rs6000_savres_strategy): Do not select {SAVE,REST}_MULTIPLE if shrink-wrapping separate components. (rs6000_get_separate_components): Assert we do not have those strategies selected. From-SVN: r241297
Diffstat (limited to 'gcc/tree-vrp.c')
0 files changed, 0 insertions, 0 deletions