diff options
author | Jeff Law <law@redhat.com> | 2006-03-22 11:00:50 -0700 |
---|---|---|
committer | Jeff Law <law@gcc.gnu.org> | 2006-03-22 11:00:50 -0700 |
commit | 4dc7782d15938a44634f16465a4dab55a25d70d2 (patch) | |
tree | 58482afa97ec4ac7799ec5dc1d3281460d546f2f /gcc/loop-unroll.c | |
parent | 906ac235a5ee616f47cbd4c526c44cd504470cff (diff) | |
download | gcc-4dc7782d15938a44634f16465a4dab55a25d70d2.tar.gz |
loop-unroll.c (analyze_iv_to_split_insn): Handle iv_analyze_result returning false.
* loop-unroll.c (analyze_iv_to_split_insn): Handle
iv_analyze_result returning false.
From-SVN: r112289
Diffstat (limited to 'gcc/loop-unroll.c')
-rw-r--r-- | gcc/loop-unroll.c | 12 |
1 files changed, 11 insertions, 1 deletions
diff --git a/gcc/loop-unroll.c b/gcc/loop-unroll.c index 6ef59476657..5c28eaf2f19 100644 --- a/gcc/loop-unroll.c +++ b/gcc/loop-unroll.c @@ -1670,7 +1670,17 @@ analyze_iv_to_split_insn (rtx insn) return NULL; ok = iv_analyze_result (insn, dest, &iv); - gcc_assert (ok); + + /* This used to be an assert under the assumption that if biv_p returns + true that iv_analyze_result must also return true. However, that + assumption is not strictly correct as evidenced by pr25569. + + Returning NULL when iv_analyze_result returns false is safe and + avoids the problems in pr25569 until the iv_analyze_* routines + can be fixed, which is apparently hard and time consuming + according to their author. */ + if (! ok) + return NULL; if (iv.step == const0_rtx || iv.mode != iv.extend_mode) |