From: Eric Sunshine <sunshine@sunshineco.com>
To: Jeff King <peff@peff.net>
Cc: "Renato Botelho" <garga@freebsd.org>,
"Junio C Hamano" <gitster@pobox.com>,
"Git List" <git@vger.kernel.org>,
"Torsten Bögershausen" <tboegi@web.de>
Subject: Re: [ANNOUNCE] Git v2.7.4 (and updates to older maintenance tracks)
Date: Mon, 21 Mar 2016 00:41:57 -0400 [thread overview]
Message-ID: <CAPig+cR7d0UF08fQy5uXW8U+7rdjGSO1drMxm6LOV-KB40mwPw@mail.gmail.com> (raw)
In-Reply-To: <20160320194313.GB6288@sigill.intra.peff.net>
[cc:+Torsten]
On Sun, Mar 20, 2016 at 3:43 PM, Jeff King <peff@peff.net> wrote:
> On Sun, Mar 20, 2016 at 01:07:52PM -0400, Eric Sunshine wrote:
>> On Sun, Mar 20, 2016 at 11:32 AM, Renato Botelho <garga@freebsd.org> wrote:
>> > 2.7.4 fails to build on FreeBSD 9.x, that uses by default gcc 4.2.1. I’ve fixed it adding an extra dependency to make force it to require gcc 4.8+. Here is the output:
>> >
>> > combine-diff.c: In function 'diff_tree_combined':
>> > combine-diff.c:1391: internal compiler error: Segmentation fault: 11
>>
>> Interesting. This appears to be the same bug as [1].
>>
>> [1]: http://thread.gmane.org/gmane.comp.version-control.git/287486/focus=287789
>
> Yes. AFAICT that version of gcc is simply buggy, and we are not doing
> anything illegal or even particularly exotic. Given how old it is, I'm
> not sure it's worth worrying too much about it, but I am happy to work
> around it if somebody can figure out how to do so.
>
> I spent some time trying to bisect gcc, but had trouble getting a
> working build for a gcc that old.
I installed FreeBSD 9 and managed to reproduce the compiler crash.
After a bit of experimentation, I devised a simple work-around and
submitted it as a patch[1].
[1]: http://thread.gmane.org/gmane.comp.version-control.git/289397
next prev parent reply other threads:[~2016-03-21 4:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 21:07 [ANNOUNCE] Git v2.7.4 (and updates to older maintenance tracks) Junio C Hamano
2016-03-18 8:29 ` Torsten Bögershausen
2016-03-20 15:32 ` Renato Botelho
2016-03-20 17:07 ` Eric Sunshine
2016-03-20 19:43 ` Jeff King
2016-03-21 4:41 ` Eric Sunshine [this message]
2016-03-21 13:33 ` Renato Botelho
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPig+cR7d0UF08fQy5uXW8U+7rdjGSO1drMxm6LOV-KB40mwPw@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=garga@freebsd.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=tboegi@web.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).