* [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
@ 2016-08-16 4:08 JonY
2016-08-16 9:20 ` Tony Kelman
0 siblings, 1 reply; 15+ messages in thread
From: JonY @ 2016-08-16 4:08 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
I have just updated the mingw-w64 cross compilers Cygwin 32bit and
64bit to mingw64-*-gcc-5.4.0-2.
Unlike the Cygwin gcc, this version DOES NOT PRESERVER C++ ABI from
gcc4. Please rebuild all your C++ libraries.
==== PLEASE RECOMPILE ALL YOUR C++ CODE FOR ABI COMPATIBILITY ====
The cross compiler can produce Win32 and Win64 native binaries. As a
cross compiler, you may use --host=i686-w64-mingw32 or
--host=x86_64-w64-mingw32 for autotools based source packages to build
for Windows.
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there. It will be in the format:
cygwin-announce-unsubscribe-you=yourdomain.com <at> cygwin.com
If you need more information on unsubscribing, start reading here:
http://sourceware.org/lists.html#unsubscribe-simple
Please read *all* of the information on unsubscribing that is available
starting at this URL.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
2016-08-16 4:08 [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64) JonY
@ 2016-08-16 9:20 ` Tony Kelman
2016-08-18 0:04 ` JonY
0 siblings, 1 reply; 15+ messages in thread
From: Tony Kelman @ 2016-08-16 9:20 UTC (permalink / raw)
To: cygwin
> 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):
# check build prereqs
curl --version
patch --version
python --version
g++ --version
m4 --version
cmake --version
7z -h
i686-w64-mingw32-gcc --version
i686-w64-mingw32-g++ --version
i686-w64-mingw32-gfortran --version
# end of build prereq checks
git clone https://github.com/JuliaLang/julia -b release-0.5
cd julia
echo 'XC_HOST = i686-w64-mingw32' > Make.user
make -j8 test
At the end of this, roughly an hour later, I see
JULIA usr/lib/julia/sys.o
Please submit a bug report with steps to reproduce this fault, and any error messages that follow (in their entirety). Thanks.
Exception: EXCEPTION_ACCESS_VIOLATION at 0xc5e821 -- unknown function (ip: 00C5E821)
while loading sysimg.jl, in expression starting on line 6
unknown function (ip: 00C5E820)
unknown function (ip: 00C5ED73)
unknown function (ip: 00C5ED73)
unknown function (ip: 04B86E87)
unknown function (ip: FFFFFFFE)
...
instead of finishing building and executing the tests as expected.
Thanks,
Tony
--
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
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
2016-08-16 9:20 ` Tony Kelman
@ 2016-08-18 0:04 ` JonY
2016-08-18 9:35 ` Tony Kelman
2016-08-20 0:35 ` Yaakov Selkowitz
0 siblings, 2 replies; 15+ messages in thread
From: JonY @ 2016-08-18 0:04 UTC (permalink / raw)
To: cygwin
[-- 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 --]
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
2016-08-18 0:04 ` JonY
@ 2016-08-18 9:35 ` Tony Kelman
2016-08-18 9:39 ` JonY
2016-08-20 0:35 ` Yaakov Selkowitz
1 sibling, 1 reply; 15+ messages in thread
From: Tony Kelman @ 2016-08-18 9:35 UTC (permalink / raw)
To: JonY, cygwin
> 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.
How long does building the cross-compiler from your cygport take, usually?
I could try that and let you know if just applying the patch from
https://gcc.gnu.org/viewcvs/gcc/trunk/gcc/config/i386/winnt.c?r1=232828&r2=232827&pathrev=232828
would fix matters. Not sure how many other packaging changes you'd need
to go from 5.4.0 to 6.1.0. (And 6.2 should be coming shortly.)
According to the discussion in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66655
the underlying issue may have also been a problem for cygwin targets,
but I do much less testing there as Julia relies on async IO (via a fork
of libuv) that cygwin doesn't provide.
-Tony
--
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
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
2016-08-18 9:35 ` Tony Kelman
@ 2016-08-18 9:39 ` JonY
2016-08-18 11:51 ` Tony Kelman
0 siblings, 1 reply; 15+ messages in thread
From: JonY @ 2016-08-18 9:39 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 707 bytes --]
On 8/18/2016 08:19, Tony Kelman wrote:
>> 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.
>
> How long does building the cross-compiler from your cygport take, usually?
> I could try that and let you know if just applying the patch from
> https://gcc.gnu.org/viewcvs/gcc/trunk/gcc/config/i386/winnt.c?r1=232828&r2=232827&pathrev=232828
> would fix matters. Not sure how many other packaging changes you'd need
> to go from 5.4.0 to 6.1.0. (And 6.2 should be coming shortly.)
>
Usually a 5-6 hours per target, but my machine is underpowered, testing
would be much appreciated.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
2016-08-18 9:39 ` JonY
@ 2016-08-18 11:51 ` Tony Kelman
2016-08-18 16:15 ` Tony Kelman
0 siblings, 1 reply; 15+ messages in thread
From: Tony Kelman @ 2016-08-18 11:51 UTC (permalink / raw)
To: JonY, cygwin
>> How long does building the cross-compiler from your cygport take, usually?
>> I could try that and let you know if just applying the patch from
>> https://gcc.gnu.org/viewcvs/gcc/trunk/gcc/config/i386/winnt.c?r1=232828&r2=232827&pathrev=232828
>> would fix matters. Not sure how many other packaging changes you'd need
>> to go from 5.4.0 to 6.1.0. (And 6.2 should be coming shortly.)
>
>
> Usually a 5-6 hours per target, but my machine is underpowered, testing
> would be much appreciated.
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.
-Tony
--
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
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
2016-08-18 11:51 ` Tony Kelman
@ 2016-08-18 16:15 ` Tony Kelman
2016-08-18 16:37 ` JonY
0 siblings, 1 reply; 15+ messages in thread
From: Tony Kelman @ 2016-08-18 16:15 UTC (permalink / raw)
To: JonY, cygwin
> 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
--
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
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
2016-08-18 16:15 ` Tony Kelman
@ 2016-08-18 16:37 ` JonY
2016-08-19 19:06 ` Tony Kelman
0 siblings, 1 reply; 15+ messages in thread
From: JonY @ 2016-08-18 16:37 UTC (permalink / raw)
To: Tony Kelman, cygwin
[-- 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 --]
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
2016-08-18 0:04 ` JonY
2016-08-18 9:35 ` Tony Kelman
@ 2016-08-20 0:35 ` Yaakov Selkowitz
2016-08-20 1:52 ` JonY
1 sibling, 1 reply; 15+ messages in thread
From: Yaakov Selkowitz @ 2016-08-20 0:35 UTC (permalink / raw)
To: cygwin
On Thu, 2016-08-18 at 07:13 +0800, JonY wrote:
> Yaakov,
>
> Can you restore 4.9.2-2 as previous? Thanks.
Done. Â Once calm next runs, 4.9.2-2 will be previous, 5.4.0-2 current,
and the previous 5.x test releases have been removed.
--
Yaakov
--
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
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
2016-08-20 0:35 ` Yaakov Selkowitz
@ 2016-08-20 1:52 ` JonY
0 siblings, 0 replies; 15+ messages in thread
From: JonY @ 2016-08-20 1:52 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 317 bytes --]
On 8/20/2016 05:54, Yaakov Selkowitz wrote:
> On Thu, 2016-08-18 at 07:13 +0800, JonY wrote:
>> Yaakov,
>>
>> Can you restore 4.9.2-2 as previous? Thanks.
>
> Done. Once calm next runs, 4.9.2-2 will be previous, 5.4.0-2 current,
> and the previous 5.x test releases have been removed.
>
>
Thanks!
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2017-02-21 14:45 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-08-16 4:08 [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64) 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
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
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).