mirror of
https://github.com/git/git.git
synced 2026-01-09 01:34:00 +00:00
varint: use explicit width for integers
The varint subsystem currently uses implicit widths for integers. On the one hand we use `uintmax_t` for the actual value. On the other hand, we use `int` for the length of the encoded varint. Both of these have known maximum values, as we only support at most 16 bytes when encoding varints. Thus, we know that we won't ever exceed `uint64_t` for the actual value and `uint8_t` for the prefix length. Refactor the code to use explicit widths. Besides making the logic platform-independent, it also makes our life a bit easier in the next commit, where we reimplement "varint.c" in Rust. Suggested-by: Ezekiel Newren <ezekielnewren@gmail.com> Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
committed by
Junio C Hamano
parent
cb2badb4db
commit
f366bfe16b
@@ -1807,7 +1807,7 @@ static struct cache_entry *create_from_disk(struct mem_pool *ce_mem_pool,
|
||||
|
||||
if (expand_name_field) {
|
||||
const unsigned char *cp = (const unsigned char *)name;
|
||||
size_t strip_len, previous_len;
|
||||
uint64_t strip_len, previous_len;
|
||||
|
||||
/* If we're at the beginning of a block, ignore the previous name */
|
||||
strip_len = decode_varint(&cp);
|
||||
@@ -2655,8 +2655,10 @@ static int ce_write_entry(struct hashfile *f, struct cache_entry *ce,
|
||||
hashwrite(f, ce->name, len);
|
||||
hashwrite(f, padding, align_padding_size(size, len));
|
||||
} else {
|
||||
int common, to_remove, prefix_size;
|
||||
int common, to_remove;
|
||||
uint8_t prefix_size;
|
||||
unsigned char to_remove_vi[16];
|
||||
|
||||
for (common = 0;
|
||||
(common < previous_name->len &&
|
||||
ce->name[common] &&
|
||||
|
||||
Reference in New Issue
Block a user