From: JonY <jon_y@users.sourceforge.net>
To: cygwin@cygwin.com, jon.turney@dronecode.org.uk
Subject: Re: [ANNOUNCEMENT] Updated: mingw64-{i686,x86_64}-gcc-5.4.0-3 (x86/x86_64)
Date: Sat, 12 Nov 2016 16:09:00 -0000 [thread overview]
Message-ID: <58269BB6.3080903@users.sourceforge.net> (raw)
In-Reply-To: <CY1PR0201MB07961BCDFE5B3445EF1E66A6A7BB0@CY1PR0201MB0796.namprd02.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 982 bytes --]
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.
[-- Attachment #1.2: 0xD4EBC740.asc --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2016-11-12 4:34 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 [this message]
2016-11-23 2:35 ` Jon Turney
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=58269BB6.3080903@users.sourceforge.net \
--to=jon_y@users.sourceforge.net \
--cc=cygwin@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/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).