Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932278AbXJEVRd (ORCPT ); Fri, 5 Oct 2007 17:17:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1763457AbXJEVRZ (ORCPT ); Fri, 5 Oct 2007 17:17:25 -0400 Received: from ns.suse.de ([195.135.220.2]:39613 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1763034AbXJEVRZ (ORCPT ); Fri, 5 Oct 2007 17:17:25 -0400 From: Andreas Schwab To: Timur Tabi Cc: Jan Engelhardt , Linux Kernel Mailing List Subject: Re: __LITTLE_ENDIAN vs. __LITTLE_ENDIAN_BITFIELD References: <4706822D.4070509@freescale.com> <470691EB.7020209@freescale.com> <470694E0.7030408@freescale.com> <47069982.9030009@freescale.com> X-Yow: I'm thinking about DIGITAL READ-OUT systems and computer-generated IMAGE FORMATIONS.. Date: Fri, 05 Oct 2007 23:17:22 +0200 In-Reply-To: <47069982.9030009@freescale.com> (Timur Tabi's message of "Fri\, 05 Oct 2007 15\:07\:30 -0500") 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 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 987 Lines: 23 Timur Tabi writes: > Then I don't understand that point of defining __LITTLE_ENDIAN_BITFIELD. > What does it mean for a C-level bitfield ordering to be little-endian if > the processor is BIG_ENDIAN? Byte endianess and bit endianness are orthogonal concecpts. A cpu can have insns using both little and big endian bit addressing (btst vs. bftst on m68k). The bitfield ordering is a property of the ABI and may even be different from how the cpu numbers the bits in its ISA. 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." - 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/