diff options
author | law <law@138bc75d-0d04-0410-961f-82ee72b054a4> | 2015-04-15 12:24:28 +0000 |
---|---|---|
committer | law <law@138bc75d-0d04-0410-961f-82ee72b054a4> | 2015-04-15 12:24:28 +0000 |
commit | b803a3c1e28305fd4c5c50972ee177c471fc7785 (patch) | |
tree | 1d0879dbbab7c2c5b15c92110904392c69270b07 /gcc/cse.c | |
parent | 1c543545f83ca31df79487ba5698fe89029ee36c (diff) | |
download | gcc-b803a3c1e28305fd4c5c50972ee177c471fc7785.tar.gz |
PR rtl-optimization/42522
* cse.c (fold_rtx): Try to simplify a ZERO_EXTRACT or
SIGN_EXTRACT as a whole object rather than simplifying
its operand.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@222125 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/cse.c')
-rw-r--r-- | gcc/cse.c | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/gcc/cse.c b/gcc/cse.c index 2a33827a61c..d7638f051f3 100644 --- a/gcc/cse.c +++ b/gcc/cse.c @@ -3150,6 +3150,15 @@ fold_rtx (rtx x, rtx_insn *insn) { case MEM: case SUBREG: + /* The first operand of a SIGN/ZERO_EXTRACT has a different meaning + than it would in other contexts. Basically its mode does not + signify the size of the object read. That information is carried + by size operand. If we happen to have a MEM of the appropriate + mode in our tables with a constant value we could simplify the + extraction incorrectly if we allowed substitution of that value + for the MEM. */ + case ZERO_EXTRACT: + case SIGN_EXTRACT: if ((new_rtx = equiv_constant (x)) != NULL_RTX) return new_rtx; return x; |