From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Cc: JonY <jon_y@users.sourceforge.net>
Subject: Re: [ANNOUNCEMENT] Updated: mingw64-{i686,x86_64}-gcc-5.4.0-3 (x86/x86_64)
Date: Wed, 23 Nov 2016 02:35:00 -0000 [thread overview]
Message-ID: <1c4f12f8-73d1-7a35-dcaa-ef9867ea664c@dronecode.org.uk> (raw)
In-Reply-To: <58269BB6.3080903@users.sourceforge.net>
On 12/11/2016 04:33, JonY wrote:
> On 11/11/2016 22:06, Tony Kelman wrote:
>>> I have just updated the mingw-w64 cross compilers Cygwin 32bit and
>>> 64bit to mingw64-{i686,x86_64}-gcc-5.4.0-3.
>>
>> Hi Jon,
>>
>> What will be left as prev? 5.4.0-2, or the last 4.9 build? Can you
>> help raise https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77333? The
>> interprocedural analysis that was added for gcc 5 is deeply buggy on
>> mingw targets, resulting in miscompiling C++ libraries like LLVM.
>> This is keeping me on gcc 4 indefinitely until it gets fixed. I may
>> have to abandon gcc and switch to clang due to this, but there are
>> many libraries that have broken build systems that behave incorrectly
>> when you try to use clang on Windows.
>>
>> I'll use time machine if that's my only way to keep getting gcc 4,
>> but this bug in gcc should really be fixed or it's going to start
>> showing up in cygwin-mingw-cross and msys2 packages.
>>
>
> Jon,
>
> Can you make 4.9 the previous version? Thanks.
Sorry, the files for 4.9.3-1 are no longer on sourceware.
I guess they got removed when you uploaded 5.3.0-3 (28/02/16)
Sorry, I guess you'll have to rebuild as gcc-4.9.3-2 and upload that, if
this is really needed.
--
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:[~2016-11-22 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 13:12 JonY
2016-11-11 14:50 ` Tony Kelman
2016-11-12 16:09 ` JonY
2016-11-23 2:35 ` Jon Turney [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=1c4f12f8-73d1-7a35-dcaa-ef9867ea664c@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=jon_y@users.sourceforge.net \
/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).