Re: [RFC PATCH v5 0/8] rebase-interactive

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 26, 2018, 18:00 UTC
Message-ID: <xmqqd0zqd8dw.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <9ca76d31-828d-0b6f-5069-375792c1f55d@jeffhostetler.com>

Jeff Hostetler <git@jeffhostetler.com> writes:

> I am concerned that the above compiler error message says that uintmax_t
> is defined as an "unsigned long" (which is defined as *at least* 32 bits,
> but not necessarily 64.  But a uint64_t is defined as a "unsigned long long"
> and guaranteed as a 64 bit value.

On a platform whose uintmax_t is u32, is it realistic to expect that we would be able to use u64, even if we explicitly ask for it, in the first place?

In other words, on a platform that handles uint64_t, I would expect uintmax_t to be wide enough to hold an uint64_t value without truncation.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.