This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/32398] [4.3 Regression] checking for suffix of object files... configure: error: cannot compute suffix of f object files: cannot compile
- From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 9 Jul 2007 22:01:59 -0000
- 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
- References: <bug-32398-276@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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