Home My Page Projects Code Snippets Project Openings SML/NJ
Summary Activity Forums Tracker Lists Tasks Docs Surveys News SCM Files

SCM Repository

[smlnj] View of /sml/trunk/READMES/110.32-README.html
ViewVC logotype

View of /sml/trunk/READMES/110.32-README.html

Parent Directory Parent Directory | Revision Log Revision Log

Revision 780 - (download) (as text) (annotate)
Tue Jan 30 22:45:26 2001 UTC (20 years, 7 months ago) by blume
File size: 3926 byte(s)
merging changes from private devel branch
    <title>SML/NJ Version 110.32 NEWS</title>

  <body bgcolor="white">
   <center><h1>Standard ML of New Jersey<BR>
        Version 110.32, December 22, 2000</h1>

      <a href=http://cm.bell-labs.com/cm/cs/what/smlnj/index.html>
      Home page</a>

<h2> Warning </h2>
  	This version is intended for compiler hackers. The 
	version ought to be quite stable, however we have not run
	our full regression testing.


  This version is being used to check point a large number of changes 
  to MLRISC, which now uses infinite precision integers on all
  architectures. We have run the Basis regressions tests so the
  changes ought to be fairly robust.   
  There are a number of other CM, Basis, and Tool related changes as

<center><h3>MLRISC </h3></center>
<h3> Fixes </h3>
    This change fixes two problems:


<p><li>   There was a proliferation of constructors in MLRISC to
	  handle integers of various sizes, e.g.
    LI of int   | LI32 of Int32.int  | LI64 of Int64.int
	   which are all replaced with
    LI of IntInf.int

<p><li>   There is the ever nagging question of cross compiling to

<h3>Compilation Speed</h3>
    The x86 compiling the compiler is 9% slower than 110.31, however,
    a lot of this, and more, can be recovered. The compiler presently
    uses infinite precision in the front end (AST creation), which is converted to 31
    and 32 bit integers in the middle end (FLINT and CPS), and then
    converted back to infinite precision in MLRISC (with the current 
    Infinite precision in the middle end will allow a uniform
    treatment of optimizations across words and integers of different
    widths/sizes. Currently, most optimizations are biased towards
    integers and words represented in 31 bits only.

<h3>  What's next</h3>
    Not in chronological order:

<li>    Use infinite precision in the middle end to allow a 
	cleaner and more uniform optimization module for arithmetic.

<p><li>	Support for the generation of infinite precision values
        in the back end.

<p><li>	 Changes to support the single toplevel declaration:
   structure LargeInt = IntInf


<center><h3>Basis </h3></center>
    Added the missing bit level functions to the Basis <tt>IntInf</tt>

<center><h3>Tools </h3></center>
    Improvements to the 'nowhere' tool to handle OR-patterns.
    The nowhere tool is a syntactic extension that allows for
    guarded patterns. See MLRISC/Tools/Doc/nowhere.tex.

<center><h3>CM </h3></center>
  <li> Added a new "dir" tool to CM's toolset; this can simplify writing
    CM descriptions (see the manual)
<p><li> Made some modifications to CM's "Tools" API and documented everything

<p><li>    CM now leaves exceptions (from the compiler) alone if they are not
    expected; this causes such exceptions to travel up to the top-level
    where they are reported as usual
<p><li>    Eliminated the "[wrote ...]" progress message in favor of reporting
    some size information for the generated binfile instead
<p><li>    Removed source code for some project-in-progress that is not ready
    for prime-time (yet)
<p><li>    Made anchor environments ("bind:"-option for class "cm") inter-operate
    in a more useful way with CMB.make 
    <font size=-2>
    <address><a href="mailto:george@research.bell-labs.com">
		Lal George</a></address>
<!-- Created: Thu Aug  6 00:13:09 EDT 1998 -->
<!-- hhmts start -->
Last modified: Sat Dec 23 11:23:17 EST 2000
<!-- hhmts end -->

ViewVC Help
Powered by ViewVC 1.0.0