public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Tony Kelman <tony@kelman.net>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
Date: Tue, 16 Aug 2016 09:20:00 -0000	[thread overview]
Message-ID: <DM2PR0201MB079940970D55C5E9019AA53DA7130@DM2PR0201MB0799.namprd02.prod.outlook.com> (raw)
In-Reply-To: <announce.57B25054.3020401@gmail.com>

> 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

  reply	other threads:[~2016-08-16  7:57 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 [this message]
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

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=DM2PR0201MB079940970D55C5E9019AA53DA7130@DM2PR0201MB0799.namprd02.prod.outlook.com \
    --to=tony@kelman.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).