From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32361 invoked by alias); 9 Mar 2010 19:44:10 -0000 Received: (qmail 32352 invoked by uid 22791); 9 Mar 2010 19:44:09 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mail2.rz.htw-berlin.de (HELO mail2.rz.htw-berlin.de) (141.45.10.102) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 09 Mar 2010 19:44:04 +0000 Envelope-to: gcc-help@gcc.gnu.org Received: from e178085094.adsl.alicedsl.de ([85.178.85.94] helo=[192.168.178.6]) by mail2.rz.htw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Np5LW-000FT8-7j for gcc-help@gcc.gnu.org; Tue, 09 Mar 2010 20:44:02 +0100 Message-ID: <4B96A501.1000806@htw-berlin.de> Date: Tue, 09 Mar 2010 19:44:00 -0000 From: Thomas Martitz Reply-To: thomas.martitz@student.htw-berlin.de User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100307 Lightning/1.0b1 Icedove/3.0.3 MIME-Version: 1.0 To: gcc-help@gcc.gnu.org Subject: Re: Problems migrating to gcc 4.4.3&eabi - apparently a gcc bug References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-HTW-SPAMINFO: this message was scanned by eXpurgate (http://www.eleven.de) X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2010-03/txt/msg00124.txt.bz2 Am 09.03.2010 20:39, schrieb John (Eljay) Love-Jensen: > Hi Thomas, > > Is this a factor...? > > """ > Note that the effectiveness of aligned attributes may be limited by inherent > limitations in your linker. On many systems, the linker is only able to > arrange for variables to be aligned up to a certain maximum alignment. (For > some linkers, the maximum supported alignment may be very very small.) If > your linker is only able to align variables up to a maximum of 8 byte > alignment, then specifying aligned(16) in an __attribute__ will still only > provide you with 8 byte alignment. See your linker documentation for further > information. > """ > > http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html > http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html > > Do you know if the linker being used supports the alignment your code is > requesting on your platform? > > Sincerely, > --Eljay > > It doesn't have anything to with the linker. The example code I posted shows the bug even before being linked or assembled. And I'm not searching for help on aligning stuff, I'm searching for help regarding the buggy register allocation for subroutine calls. Best regards.