public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: JonY <10walls@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-1 (x86/x86_64) (Testing)
Date: Sun, 07 Aug 2016 05:34:00 -0000	[thread overview]
Message-ID: <57A67CEE.9020809@gmail.com> (raw)
In-Reply-To: <DM2PR0201MB0799DF9F8C904907F6E226B4A7190@DM2PR0201MB0799.namprd02.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]

On 8/6/2016 14:58, Tony Kelman wrote:
> Have you backported the patch for GCC bug 66655 here? I was expecting
> this to miscompile LLVM and cause test failures when building the Julia
> language, as I've seen for all other GCC 5.x versions on mingw targets.
> The fix was https://gcc.gnu.org/viewcvs/gcc/trunk/gcc/config/i386/winnt.c?r1=232828&r2=232827&pathrev=232828
> which is only on gcc 6, it has not been applied to the gcc-5 branch
> https://gcc.gnu.org/viewcvs/gcc/branches/gcc-5-branch/gcc/config/i386/winnt.c?view=log
> 

Nope, just vanilla 5.4.0.

> I was expecting the following to fail, but surprisingly it seems okay.
> (It's large and would take an hour or more for you to reproduce this,
> probably no need since it's working so far):
> 
> # check build prereqs
> curl --version
> patch --version
> python --version
> g++ --version
> m4 --version
> cmake --version
> 7z -h
> x86_64-w64-mingw32-gcc --version
> x86_64-w64-mingw32-g++ --version
> x86_64-w64-mingw32-gfortran --version
> # end of build prereq checks
> git clone https://github.com/JuliaLang/julia -b release-0.5
> cd julia
> mkdir -p usr/bin # I'll need to fix Julia's build system for libvtv
> cp /usr/x86_64-w64-mingw32/sys-root/mingw/bin/libvtv-0.dll usr/bin
> make -j8 test # defaults to cross-compile when build env is cygwin
> 

Does Julia depend on C++11 features? I'm not familiar with it. How big
is it compared to say, QT?




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2016-08-07  0:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-06  2:02 JonY
2016-08-06 13:19 ` Tony Kelman
2016-08-07  5:34   ` JonY [this message]
2016-08-07 15:31     ` Tony Kelman
2016-08-08  4:47 ` Yaakov Selkowitz
2016-08-08 13: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=57A67CEE.9020809@gmail.com \
    --to=10walls@gmail.com \
    --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).