From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14536 invoked by alias); 14 Jul 2004 03:46:36 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 14529 invoked from network); 14 Jul 2004 03:46:35 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 14 Jul 2004 03:46:35 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i6E3kYe1030372; Tue, 13 Jul 2004 23:46:34 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i6E3kY021559; Tue, 13 Jul 2004 23:46:34 -0400 Received: from livre.redhat.lsd.ic.unicamp.br (vpn64-1.boston.redhat.com [172.16.66.1]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id i6E3kWVZ025269; Tue, 13 Jul 2004 23:46:33 -0400 Received: from livre.redhat.lsd.ic.unicamp.br (livre.redhat.lsd.ic.unicamp.br [127.0.0.1]) by livre.redhat.lsd.ic.unicamp.br (8.12.11/8.12.11) with ESMTP id i6E3kWKp031070; Wed, 14 Jul 2004 00:46:32 -0300 Received: (from aoliva@localhost) by livre.redhat.lsd.ic.unicamp.br (8.12.11/8.12.11/Submit) id i6E3kVoj031067; Wed, 14 Jul 2004 00:46:31 -0300 To: Richard Sandiford Cc: Kazu Hirata , gcc-patches@gcc.gnu.org Subject: Re: add h8sx support to h8300 References: <20040621.102356.74724063.kazu@cs.umass.edu> <87fz83f456.fsf@redhat.com> <87zn6aevpa.fsf@redhat.com> <873c42e8rb.fsf@redhat.com> <87r7rh8hx8.fsf@redhat.com> From: Alexandre Oliva Organization: Red Hat Global Engineering Services Compiler Team Date: Wed, 14 Jul 2004 12:49:00 -0000 In-Reply-To: <87r7rh8hx8.fsf@redhat.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2004-07/txt/msg01434.txt.bz2 On Jul 12, 2004, Richard Sandiford wrote: > The built-in-setjmp.c -O3 -fomit-frame-pointer failure (which, to remind > anyone else reading, is there with and without the patch below) does show > up a problem. And this might well be the problem you were trying to explain > above. (Sorry if so! I couldn't quite follow what you were saying.) Yup, exactly the same problem. > So it seems you just can't have a register class that includes only > the frame pointer. Yup. > ! if (!regs_ever_live[HFP_REG]) > ! return NO_REGS; I had both HFP_REG and FP_REG at some point. I thought this would minimize the risk of running into the failure case. Don't you think so? -- Alexandre Oliva http://www.ic.unicamp.br/~oliva/ Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org} Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}