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

From: Eric Sunshine <sunshine@sunshineco.com>
Date: Feb 29, 2016, 16:28 UTC
Message-ID: <CAPig+cQkP++rnE4L1QSr-sW8VkS8ce7CyY9KAscebLao2Hw73A@mail.gmail.com>
In-Reply-To: <20160229101808.GD2950@sigill.intra.peff.net>

On Mon, Feb 29, 2016 at 5:18 AM, Jeff King <peff@peff.net> wrote:

Show 21 quoted lines

> On Sat, Feb 27, 2016 at 08:12:22AM +0100, Torsten Bögershausen wrote:
>> > Torsten, what is the compiler version (I don't have Apple compilers, but
>> > it seems plausible that older clang might have the same problem).
>>
>> That's machine is running Mac OS X 10.6, which is no longer supported
>> with updates.
>>
>>  gcc --version
>> i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3)
>> Copyright (C) 2007 Free Software Foundation, Inc.
>> This is free software; see the source for copying conditions.  There is NO
>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> Thanks. Out of curiosity, I tried to reproduce by with a build of gcc
> 4.2.1, to see if I could bisect. But it seems the toolchain is quite
> complex. After much munging, I managed to build a broken compiler (which
> I think is due to a much too-new version of bison, but I stopped
> digging).
>
> 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.