This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: altivec fix for starting_frame_offset
- From: Richard Henderson <rth at redhat dot com>
- To: David Edelsohn <dje at watson dot ibm dot com>
- Cc: Aldy Hernandez <aldyh at redhat dot com>, gcc-patches at gcc dot gnu dot org
- Date: Fri, 1 Mar 2002 16:40:20 -0800
- Subject: Re: altivec fix for starting_frame_offset
- References: <rth@redhat.com> <200203012341.SAA30050@makai.watson.ibm.com>
On Fri, Mar 01, 2002 at 06:41:58PM -0500, David Edelsohn wrote:
> Is teaching locate_and_pad_parm that virtual_outgoing_args starts
> with a fixed alignment offset from the stack pointer not worth
> considering?
I did consider it. If you'd asked me before we started down this
rat hole, I'd have said that it would be more tedious finding all
the places that compute the alignment and fix them. I'm now less
certain; it's definitely ugly either way you approach this.
I don't think it's clearly better either way.
> If we go down the currently proposed path, I am more and more
> inclined to make this approach conditional on TARGET_ALTIVEC_ABI as
> Aldy originally proposed.
I'm against this. This stuff is already confusing. Adding a
conditional when both sides are _supposed_ to work out the same
will only compound the confusion.
But as you like.
r~