Re: What's cooking in git.git (Feb 2016, #07; Thu, 25)

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 29, 2016, 17:17 UTC
Message-ID: <xmqq37sbe8qr.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CAPig+cQkP++rnE4L1QSr-sW8VkS8ce7CyY9KAscebLao2Hw73A@mail.gmail.com>

Eric Sunshine <sunshine@sunshineco.com> writes:

Show 8 quoted lines

>> Your suggestion elsewhere in the thread to just use clang instead sounds
>> good to me. :)
>
> If possible, for the moment, I'd prefer to hold off on that
> sledge-hammer approach of unconditionally making the build use clang.
> It would be nice to have a more detailed understanding of what exactly
> is triggering the Apple compiler bug, and I've been trying to find
> time to check it out on my old Mac.

The (fixed) patch posted was "on OSX 10.6, use clang by default"; I think that for majority of the users, that is a reasonable thing to do.

The result of the patch still allows those who want to see how badly old Gcc breaks to do so with "make CC=gcc", doesn't it?