From mint-bounce@lists.fishpool.fi Tue Jan 22 17:28:57 2008 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <4748086F.6050006@freesbee.fr> Date: Sat, 24 Nov 2007 12:18:07 +0100 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: mint@fishpool.com Subject: Re: [MiNT] GCC 4.2.2 and binary compatibility References: <4747F03E.4050101@freesbee.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=-1.0 tagged_above=-50.5 required=7.0 tests=BAYES_00 X-Spam-Level: Status: X-Status: X-Keywords: >>> So what do you think about removing the alignments, for structure >>> members and stack parameters ? Does it break some compatibility ? > > Alignment is part of the ABI. If you change it you are creating an > incompatible ABI. OK. There is a well-known ABI for calling TOS/MiNT. But is there a standard ABI for internal data structures alignment, as well as function calls, eventually across the static libraries ? Is GCC 2.95 the de-facto standard ? Vincent