From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26248 invoked by alias); 11 Feb 2003 22:03:17 -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 26240 invoked from network); 11 Feb 2003 22:03:16 -0000 Received: from unknown (HELO monkey.daikokuya.co.uk) (213.152.55.49) by 172.16.49.205 with SMTP; 11 Feb 2003 22:03:16 -0000 Received: from neil by monkey.daikokuya.co.uk with local (Exim 3.36 #1 (Debian)) id 18iiUg-000080-00; Tue, 11 Feb 2003 22:03:10 +0000 Date: Tue, 11 Feb 2003 22:03:00 -0000 From: Neil Booth To: Geoff Keating Cc: kenner@vlsi1.ultra.nyu.edu, gcc@gcc.gnu.org Subject: Re: Altivec + 16 byte alignment Message-ID: <20030211220310.GA32672@daikokuya.co.uk> References: <10302111906.AA19734@vlsi1.ultra.nyu.edu> <200302111924.h1BJOTA13916@desire.geoffk.org> <20030211202850.GB31585@daikokuya.co.uk> <200302112043.h1BKh6k13974@desire.geoffk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200302112043.h1BKh6k13974@desire.geoffk.org> User-Agent: Mutt/1.5.3i X-SW-Source: 2003-02/txt/msg00717.txt.bz2 Geoff Keating wrote:- > > Isn't an even better place to do it in the front end, just after parsing > > the alignment request? > > You could do it if you discovered that a user-requested stack local > needed more alignment than assign_stack_local can currently give, > but it's not clear to me that the front end will always have that > information, and certainly it doesn't have it when it's just seen the > alignment request; consider > > struct foo { > int x __attribute__((aligned (512))); > } > > which might, or might not, end up on the stack. You could diagnose that when the object of that type is declared, just like we have to make other checks (particularly in C++) at that time. Neil.