From: dewar@gnat.com (Robert Dewar)
To: gcc@gcc.gnu.org, mirih@vsoft.com, snowwolf@one2one-networks.com,
tprince@computer.org
Subject: Re: LittleEndian
Date: Mon, 29 Apr 2002 16:08:00 -0000 [thread overview]
Message-ID: <20020429215234.C3DABF28F4@nile.gnat.com> (raw)
> Why would you want such an option? If the code contains byte-order
> dependencies, it's unlikely that a compiler option would fix it. If you're
> trying to port binary data files, good luck.
Most often the reason people want this is that they think it will automatically
solve the endianess problem in porting code or data from one machine to another.
That's wrong of course, but people live in hope :-)
next reply other threads:[~2002-04-29 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 16:08 Robert Dewar [this message]
2002-04-30 5:03 ` LittleEndian Allan Sandfeld Jensen
2002-04-30 14:03 ` LittleEndian Toon Moene
2002-04-30 14:12 ` LittleEndian Allan Sandfeld Jensen
2002-04-30 14:52 ` LittleEndian Toon Moene
-- strict thread matches above, loose matches on Subject: below --
2002-04-30 5:20 LittleEndian Robert Dewar
2002-04-28 23:32 LittleEndian Miri
2002-04-29 8:22 ` LittleEndian Tim Prince
2002-04-29 14:52 ` LittleEndian Allan Sandfeld Jensen
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=20020429215234.C3DABF28F4@nile.gnat.com \
--to=dewar@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=mirih@vsoft.com \
--cc=snowwolf@one2one-networks.com \
--cc=tprince@computer.org \
/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).