From mint-bounce@lists.fishpool.fi Mon Feb 11 19:21:49 2008 From: Andreas Schwab To: Vincent =?iso-8859-1?Q?Rivi=E8re?= Cc: mint , Alan Hourihane Subject: Re: [MiNT] Binutils 2.18 + GCC 4.2.3 References: <47A9B90E.6060109@freesbee.fr> <1202738558.7695.13.camel@localhost> <47B05918.3010107@freesbee.fr> <47B0B70C.3050003@freesbee.fr> X-Yow: Hmmm... a PINHEAD, during an EARTHQUAKE, encounters an ALL-MIDGET FIDDLE ORCHESTRA... ha.. ha.. Date: Tue, 12 Feb 2008 01:17:35 +0100 In-Reply-To: <47B0B70C.3050003@freesbee.fr> ("Vincent =?iso-8859-1?Q?Rivi?= =?iso-8859-1?Q?=E8re=22's?= message of "Mon\, 11 Feb 2008 21\:58\:52 +0100") Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: schwab@suse.de Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id m1C0Lncv022023 Vincent Rivière writes: > Andreas Schwab wrote: >> The warning is coming from the compiler. If you tell the compiler that >> the biggest alignment supported by the object file format is 2 then it >> will not allow bigger alignments. You need to configure >> MAX_OFILE_ALIGNMENT as appropriate. > > I don't think it is necessary to change MAX_OFILE_ALIGNMENT, because there > is: > > #define BIGGEST_ALIGNMENT (TARGET_ALIGN_INT ? 32 : 16) > #define MAX_OFILE_ALIGNMENT BIGGEST_ALIGNMENT If you don't compile with -malign-int the biggest supported alignment is 2 bytes. Andreas. -- Andreas Schwab, SuSE Labs, schwab@suse.de SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."