From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Assorted MinGW-w64 toolchain libraries and tools
Date: Sun, 14 Feb 2016 21:43:00 -0000 [thread overview]
Message-ID: <56C0F508.5080104@cygwin.com> (raw)
In-Reply-To: <56BBDCBE.2050208@cygwin.com>
On 2016-02-10 18:58, Yaakov Selkowitz wrote:
>> (Also a newer clang+llvm would be useful, they've made a lot of
>> improvements since 3.5.)
>
> LLVM/Clang version bumps are time-consuming to get right. I actually
> looked at 3.6, but MCJIT did not work OOTB with PE/COFF targets. I'll
> have to see what the story is with 3.7.
FWIW, I have 3.7.1 ready pending a stable gcc 5.3.0 release.
--
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
next prev parent reply other threads:[~2016-02-14 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 17:51 Yaakov Selkowitz
2016-02-10 20:35 ` Tony Kelman
2016-02-11 0:58 ` Yaakov Selkowitz
2016-02-11 3:24 ` Tony Kelman
2016-02-11 3:25 ` Tony Kelman
2016-02-14 20:02 ` Tony Kelman
2016-02-14 21:43 ` Yaakov Selkowitz [this message]
2016-02-15 5:54 ` Ismail Donmez
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=56C0F508.5080104@cygwin.com \
--to=yselkowitz@cygwin.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).