From: Steven Bosscher Date: Thu, 4 Apr 2013 16:40:16 +0000 (+0000) Subject: re PR middle-end/56729 (ICE in df_insn_delete) X-Git-Tag: upstream/12.2.0~70477 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=3cfbe04dfdfe2b5137cbfa7de6362258d79ee534;p=platform%2Fupstream%2Fgcc.git re PR middle-end/56729 (ICE in df_insn_delete) PR middle-end/56729 * df-scan.c (df_insn_delete): Disable failing assert. From-SVN: r197492 --- diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 6b9c6ce..d613f58 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,8 @@ +2013-04-04 Steven Bosscher + + PR middle-end/56729 + * df-scan.c (df_insn_delete): Disable failing assert. + 2013-04-04 Kyrylo Tkachov * config/arm/arm-protos.h (arm_builtin_vectorized_function): diff --git a/gcc/df-scan.c b/gcc/df-scan.c index fdfa931..e8ee189 100644 --- a/gcc/df-scan.c +++ b/gcc/df-scan.c @@ -1158,8 +1158,17 @@ df_insn_delete (rtx insn) In any case, we expect BB to be non-NULL at least up to register allocation, so disallow a non-NULL BB up to there. Not perfect but better than nothing... */ - + /* ??? bb can also be NULL if lower-subreg.c:resolve_simple_mov emits + an insn into a sequence and then does delete_insn on it. Not sure + if that makes sense, but for now it means this assert cannot work. + See PR56738. + Disable for now but revisit before the end of GCC 4.9 stage1. */ +#if 0 gcc_checking_assert (bb != NULL || reload_completed); +#else + if (bb == NULL) + return; +#endif df_grow_bb_info (df_scan); df_grow_reg_info ();