From mint-bounce@lists.fishpool.fi Mon Feb 11 18:28:39 2008 Message-ID: <47B0B70C.3050003@freesbee.fr> Date: Mon, 11 Feb 2008 21:58:52 +0100 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Andreas Schwab 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> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id m1BNScS3005142 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 However, due to the .align semantics previously discussed, the following must be used: In gcc/config/m68k/mint.h: Remove: #define TARGET_VTABLE_ENTRY_ALIGN 16 And add : #undef ALIGN_ASM_OP #define ALIGN_ASM_OP "\t.balign\t" ##undef ASM_OUTPUT_ALIGN #define ASM_OUTPUT_ALIGN(FILE,LOG) \ if ((LOG) > 0) \ fprintf ((FILE), "%s%u\n", ALIGN_ASM_OP, 1 << (LOG)); With that, your warning should go out, and everything will be long aligned (maybe). -- Vincent Rivière