linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Glynn Clements <glynn@gclements.plus.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: C programming list <linux-c-programming@vger.kernel.org>
Subject: Re: canonical byte swap macros?
Date: Mon, 11 Jul 2005 20:23:39 +0100	[thread overview]
Message-ID: <17106.51003.40109.464025@gargle.gargle.HOWL> (raw)
In-Reply-To: <Pine.LNX.4.63.0507102100500.9524@localhost.localdomain>


Robert P. J. Day wrote:

>   is there a standard set of byte swap macros/functions for doing
> big/little endian conversion?  i have no interest in re-inventing the
> wheel and i'm sure there's a universally-recognized set of macros for
> this, no?

glibc has bswap_{16,32,64} in byteswap.h, but I don't think that they
are specified by any standard.

-- 
Glynn Clements <glynn@gclements.plus.com>

  parent reply	other threads:[~2005-07-11 19:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-11  1:02 canonical byte swap macros? Robert P. J. Day
2005-07-11  2:48 ` Jeff Woods
2005-07-11 19:23 ` Glynn Clements [this message]
2005-07-11 19:44 ` Steve Graegert

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=17106.51003.40109.464025@gargle.gargle.HOWL \
    --to=glynn@gclements.plus.com \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=rpjday@mindspring.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 NNTP newsgroup(s).