From: "Iain Sandoe" <iain@sandoe.co.uk>
To: drscholl <drscholl@users.sourceforge.net>
Cc: drscholl <drscholl@users.sourceforge.net>,
"Clayton,Keith - Programmer" <Clayton@ltcc.cc.ca.us>,
"'alex@cosmo.allay.net'" <alex@cosmo.allay.net>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Endianness and comparing IP's
Date: Sat, 06 Jan 2001 23:05:05 +0000 [thread overview]
Message-ID: <20010106231225.90F15E68A@apollo.valhalla.net> (raw)
Sat, Jan 6, 2001, drscholl wrote...
[...]
>> probably (but it wouldn't be difficult to check that anyway).
> Yes, I did verify that they are all unsigned int, not just relying on
> that. :-)
hmmm. I suppose that the literals in the macro are int by definition?
> /* convert the bytes of a 32-bit integer to little endian */
> #define BSWAP32(c)
> ((c>>24)&0xff)|((c>>8)&0xff00)|((c<<8)&0xff0000)|(c<<24)
>> (or are you convinced it is OK?)
> Seems to work fine under Solaris, otherwise nobody would be able to
> download anything because the IP address would be reversed.
works OK for me too under linuxppc (with default compiler options - got
anything weird specified?).
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-01-06 23:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 23:05 Iain Sandoe [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-06 23:37 Endianness and comparing IP's Iain Sandoe
2001-01-07 2:54 ` Keith Clayton
2001-01-08 7:16 ` Geert Uytterhoeven
2001-01-08 13:20 ` alex avriette
2001-01-06 22:28 Iain Sandoe
2001-01-06 22:39 ` drscholl
2001-01-06 0:22 Iain Sandoe
2001-01-06 22:14 ` drscholl
2001-01-05 23:26 Iain Sandoe
2001-01-05 21:45 Clayton,Keith - Programmer
2001-01-05 21:07 Jerome L Quinn
2001-01-05 20:25 alex avriette
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=20010106231225.90F15E68A@apollo.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=Clayton@ltcc.cc.ca.us \
--cc=alex@cosmo.allay.net \
--cc=drscholl@users.sourceforge.net \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.