Created
April 11, 2014 03:08
-
-
Save steshaw/10438835 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
From: Katsuhiro Ueno <katsu@riec.tohoku.ac.jp> | |
Date: Thu, 10 Apr 2014 23:16:47 +0900 | |
To: sml-evolution@mailman.cs.uchicago.edu | |
Subject: [Sml-evolution] SML# version 2.0.0 release | |
Dear SML-Evolution Colleagues, | |
We are pleased to announce the release of SML# version 2.0.0 from: | |
http://www.pllab.riec.tohoku.ac.jp/smlsharp/ | |
SML# is an extension of Standard ML with practically important | |
features, including record polymorphism, seamless interoperability | |
with C, true separate compilation and linking, and native multithread | |
support on multicore CPUs. | |
The most notable change in SML# version 2 is that the SML# compiler | |
now works with the LLVM Compiler Infrastructure. The new SML# | |
compiler compiles SML# code including all of the above features to | |
LLVM IR code and produces native code through LLVM. More than half of | |
compilation phases and library modules has been rewritten for the LLVM | |
support. These changes also greatly speed up the compilation | |
processes. | |
Due to the LLVM support, we expect that the SML# compiler can be | |
easily extended to a multi-target compiler. While this 2.0.0 release | |
only supports x86 platform, we plan to support x86-64 very soon. | |
Some more descriptions are in the following document. | |
http://www.pllab.riec.tohoku.ac.jp/smlsharp/docs/2.0/en/manual.xhtml | |
twitter account for SML# announcement: @smlsharp | |
Best regards, | |
Atsushi Ohori, Katsuhiro Ueno | |
RIEC, Tohoku University | |
_______________________________________________ | |
Sml-evolution mailing list | |
Sml-evolution@mailman.cs.uchicago.edu | |
https://mailman.cs.uchicago.edu/mailman/listinfo/sml-evolution |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment