Git development
 help / color / mirror / Atom feed
From: "René Scharfe" <l.s.r@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Patrick Steinhardt <ps@pks.im>, git@vger.kernel.org
Subject: Re: [PATCH 1/6] reftable/system: provide `REFTABLE_INLINE()` macro
Date: Wed, 1 Apr 2026 00:15:32 +0200	[thread overview]
Message-ID: <b19785af-c8cf-4fdd-a44f-d4e8a0f754d5@web.de> (raw)
In-Reply-To: <xmqqpl4jy9p0.fsf@gitster.g>

On 3/31/26 11:23 PM, Junio C Hamano wrote:
> René Scharfe <l.s.r@web.de> writes:
> 
>> On 3/31/26 1:26 PM, Patrick Steinhardt wrote:
>>> Not every compiler knows about the `inline` annotation for functions.
>>> Consequently, Git knows to define `inline` as an empty macro in case
>>> it's not available.
>>
>> Does it?  Only in compat/regex/regex_internal.h, which does not leak
>> to other code, no?
> 
> As we also do 
> 
> ifneq (,$(INLINE))
>         BASIC_CFLAGS += -Dinline=$(INLINE)
> endif
> 
> in the Makefile so we cannot tell what people do with their
> config.mak ;-).

Ah, missed that.

So setting INLINE to an empty string does nothing.  We do that for an
ancient versions of HP-UX in config.mak.uname.

When I set it to '', like we do in config.mak.uname for an ancient
version of AIX, I get lots of warnings about unused functions and
linking errors due to duplicate symbols.  I can only hope that the
pre-C99 compilers targeted by this measure can better deal with that
issue somehow.

> And obviously other projects do not share our Makefile, so it is not
> too much of stretch to say Git "knows to define", even though it may
> be more precise to say "knows to let users redefine", perhaps?

Fair enough.

René


  reply	other threads:[~2026-03-31 22:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 11:26 [PATCH 0/6] reftable: some more portability improvements Patrick Steinhardt
2026-03-31 11:26 ` [PATCH 1/6] reftable/system: provide `REFTABLE_INLINE()` macro Patrick Steinhardt
2026-03-31 18:03   ` Junio C Hamano
2026-03-31 21:12   ` René Scharfe
2026-03-31 21:23     ` Junio C Hamano
2026-03-31 22:15       ` René Scharfe [this message]
2026-03-31 22:08   ` brian m. carlson
2026-04-01 12:13     ` Patrick Steinhardt
2026-03-31 11:26 ` [PATCH 2/6] reftable/stack: don't call fsync(3p) unless provided Patrick Steinhardt
2026-03-31 18:09   ` Junio C Hamano
2026-04-01 12:13     ` Patrick Steinhardt
2026-03-31 11:26 ` [PATCH 3/6] reftable/fsck: use REFTABLE_UNUSED instead of UNUSED Patrick Steinhardt
2026-03-31 18:12   ` Junio C Hamano
2026-03-31 11:26 ` [PATCH 4/6] reftable/system: add abstraction to retrieve time in milliseconds Patrick Steinhardt
2026-03-31 11:26 ` [PATCH 5/6] reftable/system: add abstraction to mmap files Patrick Steinhardt
2026-03-31 11:26 ` [PATCH 6/6] reftable: introduce "reftable-system.h" header Patrick Steinhardt
2026-03-31 18:26   ` Junio C Hamano
2026-04-01 12:14     ` Patrick Steinhardt
2026-04-01 16:37       ` Junio C Hamano
2026-04-02  6:16         ` Patrick Steinhardt
2026-04-02  7:31 ` [PATCH v2 0/5] reftable: some more portability improvements Patrick Steinhardt
2026-04-02  7:31   ` [PATCH v2 1/5] reftable: introduce "reftable-system.h" header Patrick Steinhardt
2026-04-02  7:31   ` [PATCH v2 2/5] reftable/stack: provide fsync(3p) via system header Patrick Steinhardt
2026-04-02 18:03     ` Junio C Hamano
2026-04-02  7:31   ` [PATCH v2 3/5] reftable/fsck: use REFTABLE_UNUSED instead of UNUSED Patrick Steinhardt
2026-04-02  7:31   ` [PATCH v2 4/5] reftable/system: add abstraction to retrieve time in milliseconds Patrick Steinhardt
2026-04-02 18:27     ` Junio C Hamano
2026-04-02  7:31   ` [PATCH v2 5/5] reftable/system: add abstraction to mmap files Patrick Steinhardt

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=b19785af-c8cf-4fdd-a44f-d4e8a0f754d5@web.de \
    --to=l.s.r@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=ps@pks.im \
    /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