From: Jeff Hostetler <git@jeffhostetler.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Wink Saville <wink@saville.com>,
jeffhost@microsoft.com, Git List <git@vger.kernel.org>,
Eric Sunshine <sunshine@sunshineco.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [RFC PATCH v5 0/8] rebase-interactive
Date: Mon, 26 Mar 2018 14:33:04 -0400 [thread overview]
Message-ID: <3d845e99-e392-a62f-b83e-33b58482fc54@jeffhostetler.com> (raw)
In-Reply-To: <xmqqd0zqd8dw.fsf@gitster-ct.c.googlers.com>
On 3/26/2018 2:00 PM, Junio C Hamano wrote:
> 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.
>
I was just going by what the reported compiler error message was.
It said that "unsigned long" didn't match the uint64_t variable.
And that made me nervous.
If all of the platforms we build on define uintmax_t >= 64 bits,
then it doesn't matter.
If we do have a platform where uintmax_t is u32, then we'll have a
lot more breakage than in just the new function I added.
Thanks,
Jeff
next prev parent reply other threads:[~2018-03-26 18:33 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 4:39 [RFC PATCH v4] rebase-interactive Wink Saville
2018-03-23 4:39 ` [RFC PATCH v4] rebase-interactive: Simplify pick_on_preserving_merges Wink Saville
2018-03-23 17:10 ` Johannes Schindelin
2018-03-23 4:39 ` [RFC PATCH v4] rebase: Update invocation of rebase dot-sourced scripts Wink Saville
2018-03-23 6:26 ` Eric Sunshine
2018-03-23 21:01 ` Junio C Hamano
2018-03-23 21:18 ` Eric Sunshine
2018-03-23 17:12 ` Johannes Schindelin
2018-03-23 19:06 ` Wink Saville
2018-03-23 20:51 ` Junio C Hamano
2018-03-23 21:05 ` Wink Saville
2018-03-23 21:25 ` [RFC PATCH v5 0/8] rebase-interactive Wink Saville
2018-03-23 21:34 ` Wink Saville
2018-03-23 22:39 ` Junio C Hamano
2018-03-23 22:54 ` Wink Saville
2018-03-24 5:36 ` Wink Saville
2018-03-26 15:56 ` Junio C Hamano
2018-03-26 17:01 ` Jeff Hostetler
2018-03-26 17:57 ` Junio C Hamano
2018-03-26 18:22 ` Jeff Hostetler
2018-03-27 5:07 ` Junio C Hamano
2018-03-27 10:03 ` Jeff Hostetler
2018-03-26 18:00 ` Junio C Hamano
2018-03-26 18:33 ` Jeff Hostetler [this message]
2018-03-26 18:43 ` Wink Saville
2018-03-26 19:37 ` Junio C Hamano
2018-03-26 22:35 ` Johannes Schindelin
2018-03-23 22:27 ` Junio C Hamano
2018-03-23 21:25 ` [RFC PATCH v5 1/8] rebase-interactive: simplify pick_on_preserving_merges Wink Saville
2018-03-23 21:25 ` [RFC PATCH v5 2/8] rebase: update invocation of rebase dot-sourced scripts Wink Saville
2018-03-23 21:25 ` [RFC PATCH v5 3/8] Indent function git_rebase__interactive Wink Saville
2018-03-23 22:12 ` Junio C Hamano
2018-03-23 22:52 ` Wink Saville
2018-03-23 23:06 ` Junio C Hamano
2018-03-24 0:01 ` Wink Saville
2018-03-23 21:25 ` [RFC PATCH v5 4/8] Extract functions out of git_rebase__interactive Wink Saville
2018-03-23 22:22 ` Junio C Hamano
2018-03-24 7:20 ` Eric Sunshine
2018-03-23 21:25 ` [RFC PATCH v5 5/8] Add and use git_rebase__interactive__preserve_merges Wink Saville
2018-03-23 21:25 ` [RFC PATCH v5 6/8] Remove unused code paths from git_rebase__interactive Wink Saville
2018-03-23 21:25 ` [RFC PATCH v5 7/8] Remove unused code paths from git_rebase__interactive__preserve_merges Wink Saville
2018-03-23 21:25 ` [RFC PATCH v5 8/8] Remove merges_option and a blank line Wink Saville
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d845e99-e392-a62f-b83e-33b58482fc54@jeffhostetler.com \
--to=git@jeffhostetler.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeffhost@microsoft.com \
--cc=sunshine@sunshineco.com \
--cc=wink@saville.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).