------- Comment #18 from zadeck at naturalbridge dot com 2007-07-09 22:28 ------- Subject: Re: [4.3 Regression] checking for suffix of object files... configure: error: cannot compute suffix of f object files: cannot compile
dave at hiauly1 dot hia dot nrc dot ca wrote: > ------- 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 > > The problem that i have is it the argument pointer does not have a fixed value. it is assigned to a hard register sometimes during reload. kenny -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32398
