From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16507 invoked by alias); 14 Dec 2004 16:22:21 -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 14915 invoked from network); 14 Dec 2004 16:21:44 -0000 Received: from unknown (HELO mailout05.sul.t-online.com) (194.25.134.82) by sourceware.org with SMTP; 14 Dec 2004 16:21:44 -0000 Received: from fwd03.aul.t-online.de by mailout05.sul.t-online.com with smtp id 1CeFQe-0008Jz-00; Tue, 14 Dec 2004 17:21:36 +0100 Received: from [62.226.30.24] (ESBMZBZcYeHyHfu9r-rmVtvM+Df9Y2ELtjD6HrvAd+KqVYFsE-n58e@[62.226.30.24]) by fwd03.sul.t-online.com with esmtp id 1CeFQO-1KVUp60; Tue, 14 Dec 2004 17:21:20 +0100 Message-ID: <41BF1302.7080700@t-online.de> Date: Tue, 14 Dec 2004 16:22:00 -0000 From: bernds_cb1@t-online.de (Bernd Schmidt) User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) MIME-Version: 1.0 To: Alexandre Oliva CC: gcc@gcc.gnu.org Subject: Re: [RFC] avoiding too narrow register classes in reload References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ID: ESBMZBZcYeHyHfu9r-rmVtvM+Df9Y2ELtjD6HrvAd+KqVYFsE-n58e X-TOI-MSGID: f239227a-db31-4cf1-b795-ff999a4a2c0f X-SW-Source: 2004-12/txt/msg00512.txt.bz2 > This is what causes the problem I'm running into: if this alternative > is selected (and it will often be), we end up forced to use one of the > first two argument registers for the reload, and this will fail if the > reload is needed in the middle of a function call sequence. What does the insn that it's trying to reload look like? Bernd