From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9940 invoked by alias); 9 Jul 2007 22:02:09 -0000 Received: (qmail 9894 invoked by alias); 9 Jul 2007 22:01:59 -0000 Date: Mon, 09 Jul 2007 22:02:00 -0000 Message-ID: <20070709220159.9893.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug middle-end/32398] [4.3 Regression] checking for suffix of object files... configure: error: cannot compute suffix of f object files: cannot compile In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dave at hiauly1 dot hia dot nrc dot ca" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-07/txt/msg01144.txt.bz2 ------- Comment #17 from dave at hiauly1 dot hia dot nrc dot ca 2007-07-09 22:01 ------- Subject: Re: [4.3 Regression] checking for suffix of object files... configure: error: cannot compute suffix of f obje > ------- Comment #16 from bonzini at gnu dot org 2007-07-09 21:04 ------- > Looking out of the box, why can't we add it always, the same as we do with the > frame and stack pointer?? I wonder if the fixed/variable thing is a red > herring. >>From an ABI standpoint, the stack and argument pointers are equivalent. They are both passed in hardware registers and they both point to places on the stack on function entry. The argument pointer is *always* live when a function is entered and this never changes, even if it isn't used. So, from my standpoint, it seems reasonable to add it always (at least for hppa64). However, I believe Kenny would like a solution that avoids having to set the register as live in the entry defs (i.e., he would like to move away from having entry defs, etc). Dave -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32398