All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: git@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: [PATCH] hex.c: reduce memory footprint of sha1_to_hex static buffers
Date: Fri, 13 Feb 2015 13:41:51 -0800	[thread overview]
Message-ID: <xmqq7fvlmqu8.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1423862329-7899-1-git-send-email-sbeller@google.com> (Stefan Beller's message of "Fri, 13 Feb 2015 13:18:49 -0800")

Stefan Beller <sbeller@google.com> writes:

> 41 bytes is the exact number of bytes needed for having the returned
> hex string represented. 50 seems to be an arbitrary number, such
> that there are no benefits from alignment to certain address boundaries.

Yes, with s/seems to be/is/;

This comes from e83c5163 (Initial revision of "git", the information
manager from hell, 2005-04-07), and when dcb3450f (sha1_to_hex()
usage cleanup, 2006-05-03) introduced the "4 recycled buffers" on
top, the underlying array was left at 50 bytes long.

You can now have "I fixed Linus's bug" badge ;-)

> Signed-off-by: Stefan Beller <sbeller@google.com>
> ---
>  hex.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hex.c b/hex.c
> index 9ebc050..cfd9d72 100644
> --- a/hex.c
> +++ b/hex.c
> @@ -59,7 +59,7 @@ int get_sha1_hex(const char *hex, unsigned char *sha1)
>  char *sha1_to_hex(const unsigned char *sha1)
>  {
>  	static int bufno;
> -	static char hexbuffer[4][50];
> +	static char hexbuffer[4][41];
>  	static const char hex[] = "0123456789abcdef";
>  	char *buffer = hexbuffer[3 & ++bufno], *buf = buffer;
>  	int i;

  reply	other threads:[~2015-02-13 21:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 21:18 [PATCH] hex.c: reduce memory footprint of sha1_to_hex static buffers Stefan Beller
2015-02-13 21:41 ` Junio C Hamano [this message]
2015-02-13 21:56   ` Stefan Beller
2015-02-13 21:58     ` Linus Torvalds
2015-02-13 23:45     ` Junio C Hamano

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=xmqq7fvlmqu8.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=sbeller@google.com \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.