git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: "Junio C Hamano" <gitster@pobox.com>,
	"Torsten Bögershausen" <tboegi@web.de>
Cc: 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 23:34:07 +0100	[thread overview]
Message-ID: <56D0D2DF.1040807@web.de> (raw)
In-Reply-To: <xmqqsi0fjpez.fsf@gitster.mtv.corp.google.com>

On 2016-02-26 19.29, Junio C Hamano wrote:
> Torsten Bögershausen <tboegi@web.de> writes:
> 
>> 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.
> 
> Hmph, I am not quite sure what you meant by "I haven't digged
> deeper"; I do not think you should be debugging Apple's compiler
> (unless you have the source to it and that is your job to do so,
> that is).
> 
> In any case, merging the topic to 'master', and reverting that
> commit will leave this only this change between 'master' and the
> result.  I do not immediately spot anything trickier in the
> postimage compared to the preimage that may trickle a compiler bug,
> but what would I know without the source ;-)
> 
Digging means:
run git bisect and report the commit.
And this makes the compiler happy:
  Revert "tree-diff: catch integer overflow in combine_diff_path allocation"

    This reverts commit 5b442c4f2723211ce0d862571e88ee206bfd51bf.

Test suite passes,
( except t9115, the 2 new test cases "svn.pathnameencoding=cp932".
  More info about that later)

  reply	other threads:[~2016-02-26 22:34 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
2016-02-26 18:29   ` Junio C Hamano
2016-02-26 22:34     ` Torsten Bögershausen [this message]
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=56D0D2DF.1040807@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).