DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=PW
	kfknNEm36bwF18ignLSmx097NJn3rfNft54ecWVUIcwV6wcDnK2Bu7BGZqb4SrXX
	6gAq0LOZxRq9v0L8dPMaxJ1RBRi/qE2EoklxCD8UVbJmAYM7z1jR5noMJtKP8j05
	ldfOdIIzHkobJCXZr0sppl2iTVbLWd2JCGdD80Dzw=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
In-Reply-To: <CABWu70HKdqsiAiC9p6LaPwctvD1Tn-YuRxtqE9y39iV3Bc85_g@mail.gmail.com>
References: <CABWu70FH+jRZaAW5kkrJkr1NpekK8eEsje0X2fsUvp32wPVOeQ AT mail DOT gmail DOT com>	<541A046B DOT 6020908 AT gmail DOT com>	<CABWu70E3M-H8m0+=ad3WSQ_ecWUDGac4-EaforhqOZVD-mCFeQ AT mail DOT gmail DOT com>	<5bdd863252926ba12e07ffb37798e29c AT mail DOT gmail DOT com>	<5421EFAF DOT 8090201 AT gmail DOT com>	<CABWu70HKdqsiAiC9p6LaPwctvD1Tn-YuRxtqE9y39iV3Bc85_g AT mail DOT gmail DOT com>
Date: Thu, 25 Sep 2014 17:13:17 -0500
Message-ID: <CABWu70HPRNuXepjYQd2Kbe6AqBECohMf5dxnVaD_2-b318BApQ@mail.gmail.com>
Subject: Re: AW: ld crashes with segmentation fault when linking with libmpir.a
From: "Daniel R. Grayson" <danielrichardgrayson AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8

I've reported the bug to binutils.  Thank you for your advice, all.

On Tue, Sep 23, 2014 at 5:32 PM, Daniel R. Grayson
<danielrichardgrayson AT gmail DOT com> wrote:
> Thanks!  I have just checked, but mpir is compiled without -flto.  Indeed, their
> configure script appends -fno-lto to the command line if the user try to use
> it.
>
> On Tue, Sep 23, 2014 at 5:09 PM, JonY <10walls AT gmail DOT com> wrote:
>> On 9/24/2014 05:27, Christoph H. Hochstaetter wrote:
>>> I am experiencing 100% reproducible SIGSEGVs in ld if I use link time
>>> optimization (-flto). See https://cygwin.com/ml/cygwin/2014-08/msg00439.html
>>>
>>> What actually helped is to go back to gcc 4.8.3-2 or use experimental 4.9.0.
>>> Maybe this works for you too although the problem is actually not ld itself
>>> but the gcc linker plugin cyglto_plugin.dll.
>>>
>>> Corinna suspects that not all of DJ's and Yaakov's changes were actually
>>> merged into 4.8.3-3
>>>
>>
>> No, its the opposite, 4.8.3-2 and 4.9.0 does not contain DJ's changes.
>>
>>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple