From: JonY <10walls@gmail.com>
To: Tony Kelman <tony@kelman.net>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
Date: Thu, 18 Aug 2016 16:37:00 -0000 [thread overview]
Message-ID: <57B5C44B.4000108@gmail.com> (raw)
In-Reply-To: <DM2PR0201MB07995B3B84C1DCE4FECAF11FA7150@DM2PR0201MB0799.namprd02.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
On 8/18/2016 20:08, Tony Kelman wrote:
>> Sadly I seem to get similar-looking access violations even after rebuilding
>> 5.4.0-2 from the -src cygport with the patch for GCC bug 66655 added. So
>> maybe some other change is also needed to get this working, hopefully one
>> that is included in GCC 6. I'll have to test a cross-compilation from
>> opensuse where they already have mingw-w64 GCC 6 packaged and see if things
>> are in a better shape there.
>
> I also get a segfault when I cross-compile with GCC 6.1 from opensuse 13.2
> (needs wine to run this particular bootstrap build step), so this looks
> like it's something else. To be sure, could you test the small ipa-ra.tgz
> test case from the top of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66655
> with your build? It runs correctly with my build where I've applied the
> patch, but the larger Julia+LLVM case doesn't work. So this is something
> new, and/or https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68601 wasn't
> actually a duplicate of 66655. Will continue investigating.
>
> -Tony
>
>
The -2 build already includes the patch on the 66655 link.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-08-18 14:21 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
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 [this message]
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=57B5C44B.4000108@gmail.com \
--to=10walls@gmail.com \
--cc=cygwin@cygwin.com \
--cc=tony@kelman.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).