From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26838 invoked by alias); 16 Oct 2002 04:19:06 -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 26831 invoked from network); 16 Oct 2002 04:19:06 -0000 Received: from unknown (HELO mx2.redhat.com) (12.150.115.133) by sources.redhat.com with SMTP; 16 Oct 2002 04:19:06 -0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.11.6/8.11.6) with ESMTP id g9G4IOs17614; Wed, 16 Oct 2002 00:18:24 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g9G4J4l12514; Wed, 16 Oct 2002 00:19:04 -0400 Received: from localhost.localdomain (frothingslosh.sfbay.redhat.com [172.16.24.27]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id g9G4J3D23371; Tue, 15 Oct 2002 21:19:03 -0700 Received: (from rth@localhost) by localhost.localdomain (8.11.6/8.11.6) id g9G4J1F22274; Tue, 15 Oct 2002 21:19:01 -0700 X-Authentication-Warning: localhost.localdomain: rth set sender to rth@redhat.com using -f Date: Wed, 16 Oct 2002 02:31:00 -0000 From: Richard Henderson To: Richard Kenner Cc: gcc@gcc.gnu.org Subject: Re: Question on fixup_abnormal_edges Message-ID: <20021016041901.GC22242@redhat.com> Mail-Followup-To: Richard Henderson , Richard Kenner , gcc@gcc.gnu.org References: <10210160215.AA19349@vlsi1.ultra.nyu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10210160215.AA19349@vlsi1.ultra.nyu.edu> User-Agent: Mutt/1.4i X-SW-Source: 2002-10/txt/msg00921.txt.bz2 On Tue, Oct 15, 2002 at 10:15:43PM -0400, Richard Kenner wrote: > I don't think so. How are we supposed to ensure that the insns on that > abnormal edge are executed when the exception occurs? This is an EH edge, not an arbitrary abnormal edge. We can redirect the destination of the edge and create a new landing pad with whatever we like on it. Admittedly some of the code for that isn't written, but it's possible. It would be easier to disallow call-clobbered registers across that edge. r~