linux-mips
[Top] [All Lists]

Re: A question about architecture and byte order with RPMs

To: Alex deVries <adevries@engsoc.carleton.ca>, ralf@uni-koblenz.de
Subject: Re: A question about architecture and byte order with RPMs
From: "Greg Chesson" <greg@xtp.engr.sgi.com>
Date: Thu, 4 Dec 1997 09:17:39 -0800
Cc: SGI Linux <linux@cthulhu.engr.sgi.com>, rpm-list@redhat.com
In-reply-to: Alex deVries <adevries@engsoc.carleton.ca> "Re: A question about architecture and byte order with RPMs" (Dec 4, 12:04pm)
References: <Pine.LNX.3.95.971204114636.10196F-100000@lager.engsoc.carleton.ca>
Sender: owner-linux@cthulhu.engr.sgi.com
On Dec 4, 12:04pm, Alex deVries wrote:
> Subject: Re: A question about architecture and byte order with RPMs


> > It requires
> > going through _all_ the kernel code and possibly fixing the byteorder
> > handling.
>
> Nobody wants that.
>

I've been asking the compiler people for a storage class modifier that could
be added to type declarations.  The modifier would indicate whether the
data object is stored in big-endian or little-endian format.
The compiler would generate byte swizzles or not, depending on whether
the native execution mode agrees with the indicated storage class.

Perhaps the GCC world, being somewhat more enlightened, could do something
in this area (or perhaps already is thinking about it?).

g

<Prev in Thread] Current Thread [Next in Thread>