From: "Daniel R. Grayson" <danielrichardgrayson@gmail.com>
To: cygwin@cygwin.com
Subject: Re: AW: ld crashes with segmentation fault when linking with libmpir.a
Date: Wed, 24 Sep 2014 02:13:00 -0000 [thread overview]
Message-ID: <CABWu70HKdqsiAiC9p6LaPwctvD1Tn-YuRxtqE9y39iV3Bc85_g@mail.gmail.com> (raw)
In-Reply-To: <5421EFAF.8090201@gmail.com>
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@gmail.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
next prev parent reply other threads:[~2014-09-23 22:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 21:21 Daniel R. Grayson
2014-09-17 22:24 ` JonY
2014-09-18 1:37 ` Daniel R. Grayson
2014-09-18 2:56 ` Yaakov Selkowitz
2014-09-18 2:58 ` Daniel R. Grayson
2014-09-18 6:35 ` Daniel R. Grayson
2014-09-18 9:37 ` JonY
2014-09-18 10:09 ` Marco Atzeri
2014-09-18 12:39 ` JonY
2014-09-23 22:10 ` AW: " Christoph H. Hochstaetter
2014-09-23 22:32 ` JonY
2014-09-24 2:13 ` Daniel R. Grayson [this message]
2014-09-26 2:19 ` Daniel R. Grayson
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=CABWu70HKdqsiAiC9p6LaPwctvD1Tn-YuRxtqE9y39iV3Bc85_g@mail.gmail.com \
--to=danielrichardgrayson@gmail.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).