From: "Torsten Bögershausen" <tboegi@web.de>
To: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: What's cooking in git.git (Feb 2016, #07; Thu, 25)
Date: Fri, 26 Feb 2016 17:10:27 +0100 [thread overview]
Message-ID: <56D078F3.9070905@web.de> (raw)
In-Reply-To: <xmqqfuwgmlgy.fsf@gitster.mtv.corp.google.com>
> * jk/tighten-alloc (2016-02-22) 22 commits
> (merged to 'next' on 2016-02-24 at 78b3251)
> + ewah: convert to REALLOC_ARRAY, etc
> + convert ewah/bitmap code to use xmalloc
> + diff_populate_gitlink: use a strbuf
> + transport_anonymize_url: use xstrfmt
> + git-compat-util: drop mempcpy compat code
> + sequencer: simplify memory allocation of get_message
> + test-path-utils: fix normalize_path_copy output buffer size
> + fetch-pack: simplify add_sought_entry
> + fast-import: simplify allocation in start_packfile
> + write_untracked_extension: use FLEX_ALLOC helper
> + prepare_{git,shell}_cmd: use argv_array
> + use st_add and st_mult for allocation size computation
> + convert trivial cases to FLEX_ARRAY macros
> + use xmallocz to avoid size arithmetic
> + convert trivial cases to ALLOC_ARRAY
> + convert manual allocations to argv_array
> + argv-array: add detach function
> + add helpers for allocating flex-array structs
> + harden REALLOC_ARRAY and xcalloc against size_t overflow
> + tree-diff: catch integer overflow in combine_diff_path allocation
> + add helpers for detecting size_t overflow
> + reflog_expire_cfg: NUL-terminate pattern field
>
> Update various codepaths to avoid manually-counted malloc().
>
> Will merge to 'master'.
>
Sorry being late,
but this is what my older test system says:
CC combine-diff.o
combine-diff.c: In function ‘diff_tree_combined’:
combine-diff.c:1391: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://developer.apple.com/bugreporter> for instructions.
make: *** [combine-diff.o] Error 1
Revert "use st_add and st_mult for allocation size computation" didn't fix it.
I haven't digged deeper yet.
next prev parent reply other threads:[~2016-02-26 16:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 23:14 What's cooking in git.git (Feb 2016, #07; Thu, 25) Junio C Hamano
2016-02-26 16:10 ` Torsten Bögershausen [this message]
2016-02-26 18:29 ` Junio C Hamano
2016-02-26 22:34 ` Torsten Bögershausen
2016-02-26 23:35 ` Junio C Hamano
2016-02-27 3:29 ` Jeff King
2016-02-27 7:12 ` Torsten Bögershausen
2016-02-27 17:39 ` Torsten Bögershausen
2016-02-28 18:21 ` Junio C Hamano
2016-02-28 20:09 ` [PATCH 1/1] config.mak.uname: Darwin: Use clang for Mac OS X 10.6 tboegi
2016-02-29 10:18 ` What's cooking in git.git (Feb 2016, #07; Thu, 25) Jeff King
2016-02-29 16:28 ` Eric Sunshine
2016-02-29 17:17 ` Junio C Hamano
2016-02-29 23:37 ` Eric Sunshine
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=56D078F3.9070905@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).