From: JonY <jon_y@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
Date: Thu, 18 Aug 2016 00:04:00 -0000 [thread overview]
Message-ID: <57B4EF9D.9030903@users.sourceforge.net> (raw)
In-Reply-To: <DM2PR0201MB079940970D55C5E9019AA53DA7130@DM2PR0201MB0799.namprd02.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 816 bytes --]
On 8/16/2016 15:57, Tony Kelman wrote:
>> I have just updated the mingw-w64 cross compilers Cygwin 32bit and
>> 64bit to mingw64-*-gcc-5.4.0-2.
>
> I'm regretting only testing on 64 bit in my earlier message. I do see a
> segfault now when I build Julia with i686-w64-mingw32-gcc 5.4.0-2, that
> did not occur with 4.9.2-2. Could 4.9.2-2 be reinstated as prev? And/or
> could packaging of GCC 6 be done with a faster turnaround time? Here are
> the repro steps for compiling to 32 bit (with apologies for how long it'll
> take, it's mostly miscompilation of LLVM causing the problem):
>
Yaakov,
Can you restore 4.9.2-2 as previous? Thanks.
Normally, new versions will first show up for cygwin native gcc before
being handed down to the cross compilers. I'll see about doing a test
version.
[-- 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-08-17 23:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 4:08 JonY
2016-08-16 9:20 ` Tony Kelman
2016-08-18 0:04 ` JonY [this message]
2016-08-18 9:35 ` Tony Kelman
2016-08-18 9:39 ` JonY
2016-08-18 11:51 ` Tony Kelman
2016-08-18 16:15 ` Tony Kelman
2016-08-18 16:37 ` JonY
2016-08-19 19:06 ` Tony Kelman
2016-08-20 2:29 ` JonY
2016-08-23 7:57 ` Tony Kelman
[not found] ` <DM2PR0201MB07999847654538389BC180BAA75E0@DM2PR0201MB0799.namprd02.prod.outlook.com>
2017-02-21 13:28 ` JonY
2017-02-21 14:45 ` Tony Kelman
2016-08-20 0:35 ` Yaakov Selkowitz
2016-08-20 1:52 ` JonY
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=57B4EF9D.9030903@users.sourceforge.net \
--to=jon_y@users.sourceforge.net \
--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).