From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-announce <cygwin-announce@cygwin.com>
Subject: Updated: llvm/clang-3.4.2-3
Date: Wed, 30 Jul 2014 06:01:00 -0000 [thread overview]
Message-ID: <1406698858.2744.43.camel@YAAKOV04> (raw)
The following packages have been updated in the Cygwin distribution:
* llvm-3.4.2-3
* llvm-doc-3.4.2-3
* libllvm3.4-3.4.2-3
* libllvm-devel-3.4.2-3
* libllvm-devel-static-3.4.2-3
* clang-3.4.2-3
* clang-analyzer-3.4.2-3
* libclang-3.4.2-3
* libclang-devel-3.4.2-3
* libclang-devel-static-3.4.2-3
* python-clang-3.4.2-3
* python3-clang-3.4.2-3
* cygwin32-clang-3.4.2-1 (NEW for x86_64)
* cygwin64-clang-3.4.2-1 (NEW for x86)
The LLVM suite provides libraries and tools for code generation and
optimization. Also included is Clang, an LLVM native C/C++/ObjC
compiler, and the Clang Static Analyzer, a tool that automatically finds
bugs in code.
This release fixes basic usage of clang for the x86_64-cygwin target by
defaulting to the medium code model along with a few other minor fixes.
Please note that while clang technically works now, it still has not
been extensively tested for Cygwin and therefore (possibly serious) bugs
may remain.
I have also added cross-cygwin clang compilers for each arch.
--
Yaakov
CYGWIN-ANNOUNCE UNSUBSCRIBE INFO
================================
If you want to unsubscribe from the cygwin-announce mailing list, please
use the automated form at:
http://cygwin.com/lists.html#subscribe-unsubscribe
If this does not work, then 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@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.
reply other threads:[~2014-07-30 6:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1406698858.2744.43.camel@YAAKOV04 \
--to=yselkowitz@cygwin.com \
--cc=cygwin-announce@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).