From: Jeff King <peff@peff.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Brian Gernhardt <brian@gernhardtsoftware.com>,
Git List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Ensure __BYTE_ORDER is always set
Date: Thu, 30 Jan 2014 17:46:57 -0500 [thread overview]
Message-ID: <20140130224657.GA30478@sigill.intra.peff.net> (raw)
In-Reply-To: <20140130220233.GH27577@google.com>
On Thu, Jan 30, 2014 at 02:02:33PM -0800, Jonathan Nieder wrote:
> In an ideal world I would prefer to just rely on ntohll when it's
> decent (meaning that the '#if __BYTE_ORDER != __BIG_ENDIAN' block
> could be written as
>
> if (ntohll(1) != 1) {
> ...
> }
>
> or
>
> if (ntohll(1) == 1)
> ; /* Big endian. Nothing to do.
> else {
> ...
> }
>
> ). But compat/bswap.h already relies on knowing the endianness at
> preprocessing time so that wouldn't buy anything.
Yes, though it would simplify things because we are depending on ntohll
being defined, rather than some obscure macros.
> Another "in an ideal world" option: make the loop unconditional after
> checking that optimizers on big-endian systems realize it's a noop.
> In any event, in the real world your patch looks like the right thing
> to do.
I had the same thought when reading the original patch. The loop after
pre-processing on a big-endian system should look like:
{
size_t i;
for (i = 0; i < self->buffer_size; ++i)
self->buffer[i] = self->buffer[i];
}
It really seems like the sort of thing that any halfway decent compiler
should be able to turn into a noop. I'm OK to go that route, and if you
don't have a halfway decent compiler, tough cookies; git will waste your
precious nanoseconds doing a relatively small loop. If this loop
actually mattered, we would probably do better still to leave it in disk
order, and fix it up as-needed only when we look at a particular bitmap
(we do not typically need to look at all of them on disk).
-Peff
prev parent reply other threads:[~2014-01-30 22:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 19:55 [PATCH] Ensure __BYTE_ORDER is always set Brian Gernhardt
2014-01-30 20:45 ` Jeff King
2014-01-30 21:50 ` Jeff King
2014-01-31 2:35 ` Eric Sunshine
2014-01-30 22:12 ` Jonathan Nieder
2014-01-30 22:48 ` Jeff King
2014-01-30 23:24 ` Brian Gernhardt
2014-01-30 22:02 ` Jonathan Nieder
2014-01-30 22:46 ` Jeff King [this message]
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=20140130224657.GA30478@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=brian@gernhardtsoftware.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.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).