Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754533AbXJWHTD (ORCPT ); Tue, 23 Oct 2007 03:19:03 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753323AbXJWHSx (ORCPT ); Tue, 23 Oct 2007 03:18:53 -0400 Received: from agave.telenet-ops.be ([195.130.137.77]:44794 "EHLO agave.telenet-ops.be" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753012AbXJWHSu (ORCPT ); Tue, 23 Oct 2007 03:18:50 -0400 Date: Tue, 23 Oct 2007 09:18:42 +0200 (CEST) From: Geert Uytterhoeven To: Linus Torvalds cc: Alan Cox , Jens Axboe , Linux Kernel Development , mingo@elte.hu, Linux/m68k Subject: Re: [PATCH 09/10] Change table chaining layout In-Reply-To: Message-ID: References: <1193076664-13652-1-git-send-email-jens.axboe@oracle.com> <1193076664-13652-10-git-send-email-jens.axboe@oracle.com> <20071022211617.31f5c63d@the-village.bc.nu> <20071022224343.4abf3c96@the-village.bc.nu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1003 Lines: 26 On Mon, 22 Oct 2007, Linus Torvalds wrote: > On Mon, 22 Oct 2007, Alan Cox wrote: > > For structures, not array elements or stack objects. Does gcc now get > > aligned correct as an attribute on a stack object ? > > I think m68k stack layout still guarantees 4-byte-alignment, no? The stack pointer must be even (i.e. 2 byte-alignment). But it looks like current gcc always allocates multiples of 4 bytes on the stack, probably for performance reasons. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/