From: "Falk Tannhäuser" <falk.tannhauser@free.fr>
To: cygwin@cygwin.com
Subject: Re: Fwd: gcc-4.9.2-1 (x86_64) generates segfault during linking
Date: Fri, 07 Nov 2014 20:42:00 -0000 [thread overview]
Message-ID: <545D2E9A.1070405@free.fr> (raw)
In-Reply-To: <545C919D.4070706@gmail.com>
Am 07.11.2014 um 10:32 schrieb JonY:
> 1.7.33 fixed the incorrect behavior that unfortunately broke gcc
> __cxa_atexit usage. The next 1.7.33-0.8 should be more tolerant of the
> old .32 behavior.
>
> After 1.7.33 is officially released, gcc-4.8.3-4 and 4.9 will switch to
> the standard conformant behavior.
ACK. I confirm that the problem is gone with cygwin-1.7.33-0.8 (no need for -fno-lto anymore).
Falk
--
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
prev parent reply other threads:[~2014-11-07 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <545BE242.7020507@free.fr>
2014-11-06 21:06 ` Falk Tannhäuser
2014-11-06 22:37 ` JonY
2014-11-06 22:59 ` Falk Tannhäuser
2014-11-07 9:32 ` JonY
2014-11-07 20:42 ` Falk Tannhäuser [this message]
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=545D2E9A.1070405@free.fr \
--to=falk.tannhauser@free.fr \
--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).