From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Don't allow fast-import tree delta chains to exceed maximum depth
Date: Wed, 14 Nov 2007 00:54:34 -0500 [thread overview]
Message-ID: <20071114055434.GG14735@spearce.org> (raw)
In-Reply-To: <7vhcjpnzvq.fsf@gitster.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> wrote:
> "Shawn O. Pearce" <spearce@spearce.org> writes:
> > + uint32_t type : TYPE_BITS,
> > + pack_id : PACK_ID_BITS,
> > + depth : DEPTH_BITS;
>
> uint32_t with bit-width specifiers look somewhat funny here...
Sure. But the prior item is also uint32_t and before that a pointer
so it aligns out nice. And we're using exactly 32 bits in this field.
So it just sort of made sense to me to declare it was a uint32_t.
> > @@ -1105,7 +1108,7 @@ static int store_object(
> > unsigned pos = sizeof(hdr) - 1;
> >
> > delta_count_by_type[type]++;
> > - last->depth++;
> > + e->depth = ++last->depth++;
>
> "lvalue required as increment operand"?
>
> Wouldn't it be easier to read like this?
Yes. Good call. :-)
> diff --git a/fast-import.c b/fast-import.c
> index 7544949..d32c412 100644
> --- a/fast-import.c
> +++ b/fast-import.c
> @@ -161,7 +161,7 @@ struct object_entry
> {
> struct object_entry *next;
> uint32_t offset;
> - uint32_t type : TYPE_BITS,
> + unsigned type : TYPE_BITS,
> pack_id : PACK_ID_BITS,
> depth : DEPTH_BITS;
> unsigned char sha1[20];
> @@ -1108,7 +1108,7 @@ static int store_object(
> unsigned pos = sizeof(hdr) - 1;
>
> delta_count_by_type[type]++;
> - e->depth = ++last->depth++;
> + e->depth = last->depth + 1;
>
> hdrlen = encode_header(OBJ_OFS_DELTA, deltalen, hdr);
> write_or_die(pack_data->pack_fd, hdr, hdrlen);
> @@ -1121,8 +1121,6 @@ static int store_object(
> pack_size += sizeof(hdr) - pos;
> } else {
> e->depth = 0;
> - if (last)
> - last->depth = 0;
> hdrlen = encode_header(type, datlen, hdr);
> write_or_die(pack_data->pack_fd, hdr, hdrlen);
> pack_size += hdrlen;
> @@ -1138,6 +1136,7 @@ static int store_object(
> free(last->data);
> last->data = dat;
> last->offset = e->offset;
> + last->depth = e->depth;
> last->len = datlen;
> }
> return 0;
--
Shawn.
prev parent reply other threads:[~2007-11-14 5:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 4:48 [PATCH] Don't allow fast-import tree delta chains to exceed maximum depth Shawn O. Pearce
2007-11-14 5:45 ` Brian Downing
2007-11-14 5:46 ` Junio C Hamano
2007-11-14 5:54 ` Shawn O. Pearce [this message]
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=20071114055434.GG14735@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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;
as well as URLs for NNTP newsgroup(s).