From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12252 invoked by alias); 16 Oct 2002 02:15:03 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 12222 invoked from network); 16 Oct 2002 02:15:02 -0000 Received: from unknown (HELO vlsi1.ultra.nyu.edu) (128.122.140.213) by sources.redhat.com with SMTP; 16 Oct 2002 02:15:02 -0000 Received: by vlsi1.ultra.nyu.edu (4.1/1.34) id AA19349; Tue, 15 Oct 02 22:15:43 EDT Date: Wed, 16 Oct 2002 00:31:00 -0000 From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner) Message-Id: <10210160215.AA19349@vlsi1.ultra.nyu.edu> To: rth@redhat.com Subject: Re: Question on fixup_abnormal_edges Cc: gcc@gcc.gnu.org X-SW-Source: 2002-10/txt/msg00916.txt.bz2 Well, except for caller-save not being intelligent enough to add the instruction to the edge, rather than directly after the call instruction, everything would have worked out ok. I don't think so. How are we supposed to ensure that the insns on that abnormal edge are executed when the exception occurs?