git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org,
	"brian m. carlson" <sandals@crustytoothpaste.net>,
	Collin Funk <collin.funk1@gmail.com>,
	Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Subject: Re: [PATCH v3 0/5] bswap.h: Rework ntohl handling
Date: Wed, 16 Jul 2025 07:01:11 +0200	[thread overview]
Message-ID: <20250716050111.cw6zt2Vs@breakpoint.cc> (raw)
In-Reply-To: <xmqqple1f7ge.fsf@gitster.g>

On 2025-07-15 14:52:01 [-0700], Junio C Hamano wrote:
> Sebastian Andrzej Siewior <sebastian@breakpoint.cc> writes:
> 
> > this series continues the rework of the bswap32/64()/ nothl() handling. 
> >
> > I've been looking at recent compiler and they manage to recognize the
> > manual shifting and use an optimize opcode if available. The ntohl
> > version provided by glibc already provides an "optimized" version which
> > makes an optimisation in git almost not needed.
> > One of the motivation behind overwriting/ providing an optimized
> > version was to provide a macro instead of using a function call. One
> > libc that is still providing ntohl as a function call is musl.
> >
> > While ntohl() is provided by the libc, the ntohll() is not. I found it
> > only on Windows provided by winsock.h.
> >
> > I haven't touched the put/get_be*() macros. gcc & clang are both smart
> > enough to swap the content accordingly and perform a single store/ load.
> > Only the msvc seems to strugle here and performs multiple bytes stores/
> > loads and shifts.
> >
> > v2…v3 https://lore.kernel.org/all/20250611221444.1567638-1-sebastian@breakpoint.cc/
> >   - Fixed typos in the patch description
> 
> Thanks for updating the proposed log messages with typofixes.  I
> understand the patch text has no changes?

The patches iteself remain unchanged, only the patch description of a
few got updated.
There was only one comment regarding using endian(3). At the same time I
got the feeling to first get this through and then we can think how to
continue further. glibc optimizes ntohl already so git might not have
to. I only found musl that has a function call. I didn't look on *BSD.
It just something is needed for ntohll().

> Thanks.

Sebastian

      parent reply	other threads:[~2025-07-16  5:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15 19:12 [PATCH v3 0/5] bswap.h: Rework ntohl handling Sebastian Andrzej Siewior
2025-07-15 19:12 ` [PATCH v3 1/5] bswap.h: Add support for __BYTE_ORDER__ Sebastian Andrzej Siewior
2025-07-15 19:12 ` [PATCH v3 2/5] bswap.h: Define GIT_LITTLE_ENDIAN on msvc as little endian Sebastian Andrzej Siewior
2025-07-15 19:12 ` [PATCH v3 3/5] bswap.h: Always overwrite ntohl/ ntohll macros Sebastian Andrzej Siewior
2025-07-15 19:12 ` [PATCH v3 4/5] bswap.h: Remove optimized x86 version of bswap32/64 Sebastian Andrzej Siewior
2025-07-15 19:12 ` [PATCH v3 5/5] bswap.h: Provide a built-in based version of bswap32/64 if possible Sebastian Andrzej Siewior
2025-07-15 21:52 ` [PATCH v3 0/5] bswap.h: Rework ntohl handling Junio C Hamano
2025-07-15 22:36   ` brian m. carlson
2025-07-16  5:01   ` Sebastian Andrzej Siewior [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=20250716050111.cw6zt2Vs@breakpoint.cc \
    --to=sebastian@breakpoint.cc \
    --cc=collin.funk1@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kristofferhaugsbakk@fastmail.com \
    --cc=sandals@crustytoothpaste.net \
    /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).