This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Abort in redirect_edge_and_branch on vax at line 866
- From: Richard Henderson <rth at redhat dot com>
- To: law at redhat dot com
- Cc: Jan Hubicka <jh at suse dot cz>, John David Anglin <dave at hiauly1 dot hia dot nrc dot ca>, gcc-bugs at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Thu, 10 Jan 2002 09:14:24 -0800
- Subject: Re: Abort in redirect_edge_and_branch on vax at line 866
- References: <20020109152523.A31895@redhat.com> <28078.1010681947@porcupine.cygnus.com>
On Thu, Jan 10, 2002 at 09:59:07AM -0700, law@redhat.com wrote:
> I see that delete_insn no longer has the side effect of deleting code
> which becomes unreachable due to deleting the original insn. That makes
> me feel a lot better! Boy I need to keep up with development better.
Yep. The old delete_insn is now delete_related_insns, and iirc
is now only used from dbr_schedule. And if we can convince Eric
to finish the new dbr pass we talked about ... ;-)
> Probably the only problem that I can envision arising now would be
> looking at BLOCK_{HEAD,END} and getting back an insn that has been deleted
> and removed from the chain of insns.
Surprise! delete_insn now takes care of this as well. See
the end of remove_insn.
r~