From: "Pablo Sabater" <pabloosabaterr@gmail.com>
To: "Srujith Poojary" <poojarysrujith@gmail.com>,
"Pablo Sabater" <pabloosabaterr@gmail.com>
Cc: "Srujith A Poojary via GitGitGadget" <gitgitgadget@gmail.com>,
<git@vger.kernel.org>, "Phillip Wood" <phillip.wood123@gmail.com>,
"Usman Akinyemi" <usmanakinyemi202@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH v6] diff-delta: use safe integer arithmetic
Date: Tue, 27 Oct 2026 11:32:39 +0000 [thread overview]
Message-ID: <DMFL6539NDIW.2LN0YXSJH5VT9@gmail.com> (raw)
In-Reply-To: <CABh_KWhac74wQY3sTAFp7f_9CKKAmBWcE9wir4_1i7iZqsq8fw@mail.gmail.com>
On Tue Oct 27, 2026 at 11:01 AM WET, Srujith Poojary wrote:
> On Tue, Oct 27, 2026 at 4:03 PM Pablo Sabater <pabloosabaterr@gmail.com> wrote:
>>
>> On Tue Oct 27, 2026 at 4:51 AM WET, Srujith A Poojary via GitGitGadget wrote:
>> > From: Srujith A Poojary <poojarysrujith@gmail.com>
>> >
>> [snip]
>> >
>> > For the unpacked index allocation:
>> > - sizeof(struct unpacked_index_entry) is 12 bytes on 32-bit systems,
>> > which may be padded to 16 bytes depending on compiler alignment rules.
>>
>> l 117-125 'diff-delta.c'
>>
>> struct index_entry {
>> const unsigned char *ptr;
>> unsigned int val;
>> };
>>
>> struct unpacked_index_entry {
>> struct index_entry entry;
>> struct unpacked_index_entry *next;
>> };
>>
>> On 32 bit systems we have 4 bytes ptr + 4 bytes uint + 4 bytes ptr. I
>> don't see how it could be padded to 16.
>>
[snip]
> Hi Pablo,
>
> Thank you for reviewing the code and catching that! You are completely
> right—on 32-bit systems, the fields sum up cleanly to 16 bytes without
12 bytes, not 16.
> needing extra alignment padding.
> I have updated the commit message in v7 to reflect your exact
> breakdown. Thanks again for the thorough check!
>
> Best regards,
> Srujith
Regards,
Pablo.
next prev parent reply other threads:[~2026-10-27 11:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 3:56 [PATCH] [Outreachy PATCH] diff-delta: use safe integer arithmetic Srujith A Poojary via GitGitGadget
2026-10-23 5:04 ` Junio C Hamano
2026-10-23 5:29 ` Srujith Poojary
2026-10-23 15:30 ` Junio C Hamano
2026-10-23 16:56 ` Srujith Poojary
2026-10-23 18:45 ` Junio C Hamano
2026-10-23 5:56 ` [PATCH v2] " Srujith A Poojary via GitGitGadget
2026-10-23 15:15 ` Phillip Wood
2026-10-23 18:49 ` Junio C Hamano
2026-10-24 3:44 ` Srujith Poojary
2026-10-24 3:48 ` [PATCH v3] " Srujith A Poojary via GitGitGadget
2026-10-24 16:15 ` Junio C Hamano
2026-10-24 17:26 ` Srujith Poojary
2026-10-25 18:10 ` Junio C Hamano
2026-10-25 19:21 ` Srujith Poojary
2026-10-24 18:00 ` [PATCH v4] " Srujith A Poojary via GitGitGadget
2026-10-25 19:20 ` [PATCH v5] " Srujith A Poojary via GitGitGadget
2026-10-26 17:37 ` Junio C Hamano
2026-10-26 18:47 ` Srujith Poojary
2026-10-27 4:50 ` Srujith Poojary
2026-10-27 4:51 ` [PATCH v6] " Srujith A Poojary via GitGitGadget
2026-10-27 10:33 ` Pablo Sabater
2026-10-27 11:01 ` Srujith Poojary
2026-10-27 11:32 ` Pablo Sabater [this message]
2026-10-27 11:00 ` [PATCH v7] " Srujith A Poojary via GitGitGadget
2026-10-27 11:52 ` Pablo Sabater
2026-10-27 14:18 ` Srujith Poojary
2026-10-27 16:27 ` Junio C Hamano
2026-10-27 16:57 ` Srujith Poojary
2026-10-27 14:21 ` [PATCH v8] " Srujith A Poojary via GitGitGadget
2026-10-27 16:56 ` [PATCH v9] " Srujith A Poojary via GitGitGadget
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=DMFL6539NDIW.2LN0YXSJH5VT9@gmail.com \
--to=pabloosabaterr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=phillip.wood123@gmail.com \
--cc=poojarysrujith@gmail.com \
--cc=usmanakinyemi202@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