From: Alan Lehotsky <apl@alum.mit.edu>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: dewar@gnat.com, gcc@gcc.gnu.org
Subject: Re: Big-endian Gcc on Intel IA32
Date: Mon, 17 Dec 2001 14:00:00 -0000 [thread overview]
Message-ID: <p0433010cb84415e0c0cb@[192.168.1.254]> (raw)
In-Reply-To: <200112172104.fBHL4gw01582@penguin.transmeta.com>
At 1:04 PM -0800 12/17/01, Linus Torvalds wrote:
>In article <20011217200410.D28DAF28BE@nile.gnat.com> you write:
>><<My question to you all is: Is there a big-endian GCC available on IA32?
>> If available, who is the source of
>>contact and what is the effort involved here?
> >>>
>......
>One thing that might be helpful for portability issues like this, where
>the user _is_ willing and able to recompile the application, but maybe
>not able to find all subtly users of byte-order dependencies would be to
>allow the notion of "byte order attributes" on data structures.
>
>This can be especially useful for those architectures that actually have
>at least limited support for either byte-order (ie I think sparc64 has a
>"load as little-endian").
It ought to be possible to add a peephole to the MD file that matches the inline expansion of
htonl() or ntohl() and results in the appropriate load-endian instruction....
I don't think that any data-structure tagging would be necessary (although I admit that there
might be some utility to making things work without the programmer needing to carefully
wrap all the accesses and assignments with appropriate XtoY's)
-- Al
--
------------------------------------------------------------------------
Quality Software Management
http://home.earthlink.net/~qsmgmt
apl@alum.mit.edu
(978)287-0435 Voice
(978)808-6836 Cell
(978)287-0436 Fax
Software Process Improvement and Management Consulting
Language Design and Compiler Implementation
next prev parent reply other threads:[~2001-12-17 21:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 12:08 dewar
2001-12-17 13:10 ` Linus Torvalds
2001-12-17 14:00 ` Alan Lehotsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-23 7:26 dewar
2001-12-23 7:06 dewar
2001-12-23 7:08 ` Florian Weimer
2001-12-20 5:36 Etienne Lorrain
2001-12-19 11:47 Bernard Dautrevaux
2001-12-19 13:09 ` Linus Torvalds
2001-12-18 11:41 Morten Welinder
2001-12-18 11:42 ` Phil Edwards
2001-12-18 14:48 ` Linus Torvalds
2001-12-18 3:49 dewar
2001-12-23 6:59 ` Florian Weimer
2001-12-17 18:39 dewar
2001-12-17 18:59 ` Per Bothner
2001-12-17 13:14 dewar
2001-12-17 13:42 ` guerby
2001-12-17 13:43 ` Linus Torvalds
2001-12-17 14:22 ` guerby
2001-12-17 14:52 ` Linus Torvalds
2001-12-17 15:01 ` Richard Henderson
2001-12-17 15:12 ` Linus Torvalds
2001-12-17 15:54 ` Richard Henderson
2001-12-17 17:43 ` Linus Torvalds
2001-12-17 18:12 ` Richard Henderson
2001-12-18 11:55 ` Jason Riedy
2001-12-17 16:43 ` Ross Smith
2001-12-18 1:28 ` Florian Weimer
2001-12-17 12:00 Ghanta, Bose
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='p0433010cb84415e0c0cb@[192.168.1.254]' \
--to=apl@alum.mit.edu \
--cc=dewar@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).