SCM Repository

[smlnj] Diff of /sml/trunk/HISTORY

[smlnj] / sml / trunk / HISTORY

Diff of /sml/trunk/HISTORY

-revision 656, Fri Jun  9 03:39:04 2000 UTC
+revision 695, Mon Aug  7 23:57:38 2000 UTC
 Line 12
  Tag: <post-commit CVS tag>
  Description:
  ----------------------------------------------------------------------
+ Name: Allen Leung
+ Date: 2000/08/7 19:31:00
+ Tag: leunga-20000807-a-whole-bunch-of-stuff
+   Moby, C--, SSA, x86, machine descriptions etc.  Should only affect C--
+ and Mobdy.
+.  x86
+    a.  Fixes to peephole module by John and Dan.
+    b.  Assembly fix to SETcc by Allen.
+    c.  Fix to c-call by John.
+    d.  Fix to spilling by John.  (This one deals with the missing FSTPT case)
+    e.  Instruction selection optimization to SETcc as suggested by John.
+        For example,
+         MV(32, x, COND(32, CMP(32, LT, a, b), LI 1, LI 0))
+        should generate:
+         MOVL a, x
+         SUBL b, x
+         SHRL 31, x
+.  IR stuff
+      A bunch of new DJ-graph related algorithms added.  These
+      speed up SSA construction.
+.  SSA + Scheduling
+      Added code for SSA and scheduling to the repository
+ ----------------------------------------------------------------------
+ Name: Lal George
+ Date: 2000/07/27 11:53:14 EDT
+ Tag: lal-20000727-linux-ppc
+ Description:
+  Made changes to support Linux PPC.
+  p.s. I have confirmation that the 110.29 boot files work fine.
+ ----------------------------------------------------------------------
+ Name: Matthias Blume
+ Date: 2000/07/27 17:40:00 JST
+ Tag: blume-20000727-scripts
+ Description:
+ !!!! WARNING !!!!
+ You must recompile the runtime system!
+ !!!! WARNING !!!!
+ This is basically another round of script-enhancements:
+. sml, ml-build, and ml-makedepend accept options -D and -U to define
+    and undefine CM preprocessor symbols.
+. ml-build avoids generating a new heap image if it finds that the
+    existing one is still ok.  (The condition is that no ML file had to
+    be recompiled and all ML files are found to be older that the heap
+    file.)
+    To make this work smoothly, I also hacked the runtime system as
+    well as SMLofNJ.SysInfo to get access to the heap image suffix
+    (.sparc-solaris, ...) that is currently being used.
+    Moreover, the signature of CM.mk_standalone has changed.  See the
+    CM manual.
+. ml-makedepend accepts additional options -n, -a, and -o.  (See the
+    CM manual for details.)
+. More CM manual updates:
+     - all of the above has been documented.
+     - there is now a section describing the (CM-related) command line
+       arguments that are accepted by the "sml" command
+ ----------------------------------------------------------------------
+ Name: Matthias Blume
+ Date: 2000/07/25 16:20:00 JST
+ Tag: blume-20000725-makedepend
+ Description:
+ Added a script called ml-makedepend.  This can be used in makefiles
+ for Unix' make in a way very similar to the "makedepend" command for
+ C.
+ The script internally uses function CM.sources.
+ Synopsis:
+     ml-makedepend [-f makefile] cmfile targetname
+ The default for the makefile is "makefile" (or "Makefile" should
+ "makefile" not exist).
+ ml-makedepend adds a cmfile/targetname-specific section to this
+ makefile (after removing the previous version of this section).  The
+ section contains a single dependency specification with targetname on
+ the LHS (targetname is an arbitrary name), and a list of files derived
+ from the cmfile on the RHS.  Some of the files on the RHS are
+ ARCH/OPSYS-specific.  Therefore, ml-makedepend inserts references to
+ "make" variables $(ARCH) and $(OPSYS) in place of the corresponding
+ path names.  The makefile writer is responsible for making sure that
+ these variables have correct at the time "make" is invoked.
+ ----------------------------------------------------------------------
+ Name: Matthias Blume
+ Date: 2000/07/22 23:30:00 JST
+ Tag: blume-20000722-urlupdate
+ Description:
+ Changed BOOT and config/srcarchiveurl to point to BL server:
+     ftp://ftp.research.bell-labs.com/dist/smlnj/working/110.29/
+ ----------------------------------------------------------------------
+ Name: Matthias Blume
+ Date: 2000/07/18 18:00:00 JST
+ Tag: blume-20000718-Version_110_29
+ Description:
+. Updated src/compiler/TopLevel/main/version.sml to version 110.29
+. Updated config/version to 110.29
+. Updated config/srcarchiveurl
+. New boot files!
+    ftp://ftp.cs.princeton.edu/pub/people/blume/sml/110.29-autofetch
+ ----------------------------------------------------------------------
+ Name: Matthias Blume
+ Date: 2000/07/11 13:58:00 JST
+ Tag: blume-20000711-doctypo
+ Description:
+ Fixed a few typos in CM manual.
+ ----------------------------------------------------------------------
+ Name: Allen Leung
+ Date: 2000/06/15 00:38:00
+ Tag: leunga-20000704-sparc-x86
+. x86 peephole improvement sp += k; sp -= k => nop  [from John]
+. fix to x86 RET bug [found by Dan Grossman]
+. sparc assembly bug fix for ticc instructions [found by Fermin]
+    Affects c-- and moby only
+ ----------------------------------------------------------------------
+ Name: Matthias Blume
+ Date: 2000/07/04 15:26:00
+ Tag: blume-20000704-trigger
+ Description:
+. Improvements to CM manual.
+. SMLofNJ.Internals.BTrace.trigger reinstated as an alternative way
+    of getting a back-trace.  The function, when called, raises an
+    internal exception which explicitly carries the full back-trace history,
+    so it is unaffected by any intervening handle-raise pairs ("trivial"
+    or not).  The interactive loop will print that history once it arrives
+    at top level.
+    Short of having all exceptions implicitly carry the full history, the
+    recommended way of using this facility is:
+      - compile your program with instrumentation "on"
+      - run it, when it raises an exception, look at the history
+      - if the history is "cut off" because of some handler, go and modify
+        your program so that it explicitly calls BTrace.trigger
+      - recompile (still instrumented), and rerun; look at the full history
+ ----------------------------------------------------------------------
+ Name: Matthias Blume
+ Date: 2000/07/03 15:36:00 JST
+ Tag: blume-20000702-manual
+ Description:
+ Small corrections and updates to CM manual.
+ ----------------------------------------------------------------------
+ Name: Matthias Blume
+ Date: 2000/06/29 16:04:00 JST
+ Tag: blume-20000629-yacctool
+ Description:
+ Changes:
+. Class "mlyacc" now takes separate arguments to pass options to
+    generated .sml- and .sig-files independently.
+. Corresponding CM manual updates.
+. BTrace module now also reports call sites.  (However, for loop clusters
+    it only shows from where the cluster was entered.)  There are associated
+    modifications to core.sml, internals.{sig,sml}, btrace.sml, and btimp.sml.
+ ----------------------------------------------------------------------
+ Name: Matthias Blume
+ Date: 2000/06/27 16:51:00 JST
+ Tag: blume-20000627-noweb
+ Description:
+ Changes:
+. Implemented "subdir" and "witness" options for noweb tool.
+     This caused some slight internal changes in CM's tool implementation.
+. Fixed bug in "tool plugin" mechanism.  This is essentially cleaning
+     some remaining issues from earlier path anchor changes.
+. Updated CM manual accordingly.
+. Changed implementation of back-tracing so that I now consider it
+     ready for prime-time.
+     In particular, you don't have to explicitly trigger the back-trace
+     anymore.  Instead, if you are running BTrace-instrumented code and
+     there is an uncaught exception (regardless of whether or not it was
+     raised in instrumented code), the top-level evalloop will print
+     the back-trace.
+     Features:
+       - Instrumented and uninstrumented code work together seemlessly.
+         (Of course, uninstrumented code is never mentioned in actual
+          back-traces.)
+       - Asymptotic time- and space-complexity of instrumented code is
+         equal to that of uninstrumented code.  (This means that
+         tail-recursion is preserved by the instrumentation phase.)
+       - Modules whose code has been instrumented in different sessions
+         work together without problem.
+       - There is no penalty whatsoever on uninstrumented code.
+       - There is no penalty on "raise" expressions, even in
+         instrumented code.
+     A potential bug (or perhaps it is a feature, too):
+       A back-trace reaches no further than the outermost instrumented
+       non-trivial "raise".  Here, a "trivial" raise is one that is the
+       sole RHS of a "handle" rule.  Thus, back-traces reach trough
+            <exp> handle e => raise e
+       and even
+            <exp> handle Foo => raise Bar
+       and, of course, through
+            <exp> handle Foo => ...
+      if the exception was not Foo.
+      Back-traces always reach right through any un-instrumented code
+      including any of its "handle" expressions, trivial or not.
+    To try this out, do the following:
+      - Erase all existing binfiles for your program.
+        (You may keep binfiles for those modules where you think you
+         definitely don't need back-tracing.)
+      - Turn on back-trace instrumentation:
+           SMLofNJ.Internals.BTrace.mode (SOME true);
+      - Recompile your program.  (I.e., run "CM.make" or "use".)
+      - You may now turn instrumentation off again (if you want):
+           SMLofNJ.Internals.BTrace.mode (SOME false);
+      - Run your program as usual.  If it raises an exception that
+        reaches the interactive toplevel, then a back-trace will
+        automatically be printed.  After that, the toplevel loop
+        will print the exception history as usual.
+ ----------------------------------------------------------------------
+ Name: Matthias Blume
+ Date: 2000/06/26 09:56:46 JST
+ Tag: blume-20000626-setup
+ Description:
+ CM: - setup-parameter to "sml" added; this can be used to run arbitrary
+       ML code before and after compiling a file (e.g., to set compiler
+       flags)
+ Compiler: - improved btrace API (in core.sml, internals.{sig,sml})
+           - associated changes to btrace.sml (BTrace instrumentation pass)
+           - cleaner implementation of btimp.sml (BTrace tracing and report
+             module)
+ CM manual: * new path encoding documented
+            * description of setup-parameter to "sml" added
+ The biggest user-visible change to back-tracing is that it is no
+ longer necessary to compile all traced modules within the same
+ session.  (This was a real limitation.)
+ ----------------------------------------------------------------------
+ Name: Matthias Blume
+ Date: 2000/06/24 12:40:00 JST
+ Tag: blume-20000624-startup
+ Description:
+ Fixes startup slowdown problem.  (I was calling SrcPath.sync a _tad_
+ bit too often -- to put it mildly. :)
+ ----------------------------------------------------------------------
+ Name: Matthias Blume
+ Date: 2000/06/23 18:20:00 JST
+ Tag: blume-20000623-btrace
+ Description:
+ This updates adds a backtrace facility to aid programmers in debugging
+ their programs.  This involves the following changes:
+. Module system/smlnj/init/core.sml (structure _Core) now has hooks for
+    keeping track of the current call stack.  When programs are compiled
+    in a special mode, the compiler will insert calls to these hooks
+    into the user program.
+    "Hook" means that it is possible for different implementations of
+    back-tracing to register themselves (at different times).
+. compiler/MiscUtil/profile/btrace.sml implements the annotation phase
+    as an Absyn.dec->Absyn.dec rewrite.  Normally this phase is turned off.
+    It can be turned on using this call:
+      SMLofNJ.Internals.BTrace.mode (SOME true);
+    Turning it off again:
+      SMLofNJ.Internals.BTrace.mode (SOME false);
+    Querying the current status:
+      SMLofNJ.Internals.BTrace.mode NONE;
+    Annotated programs are about twice as big as normal ones, and they
+    run a factor of 2 to 4 slower with a dummy back-trace plugin (one
+    where all hooks do nothing).  The slowdown with a plugin that is
+    actually useful (such as the one supplied by default) is even greater,
+    but in the case of the default plugin it is still only an constant
+    factor (amortized).
+. system/Basis/Implementation/NJ/internals.{sig,sml} have been augmented
+    with a sub-structure BTrace for controlling back-tracing.  In particular,
+    the above-mentioned function "mode" controls whether the annotation
+    phase is invoked by the compiler.  Another important function is
+    "trigger": when called it aborts the current execution and causes
+    the top-level loop to print a full back-trace.
+. compiler/MiscUtil/profile/btimp.sml is the current default plugin
+    for back-tracing.  It keeps track of the dynamic call stack and in
+    addition to that it keeps a partial history at each "level" of that
+    stack.  For example, if a tail-calls b, b tail-calls c, and c tail-calls
+    d and b (at separate times, dynamically), then the report will show:
+    GOTO   d
+          /c
+    GOTO  \b
+    CALL   a
+    This shows that there was an initial non-tail call of a, then a
+    tail-call to b or c, looping behavior in a cluster of functions that
+    consist of b and c, and then a goto from that cluster (i.e., either from
+    b or from c) to d.
+    Note that (depending on the user program) the amount of information
+    that the back-trace module has to keep track of at each level is bounded
+    by a constant.  Thus, the whole implementation has the same asymptotical
+    complexity as the original program (both in space and in time).
+. compiler/TopLevel/interact/evalloop.sml has been modified to
+    handle the special exception SMLofNJ.Internals.BTrace.BTrace
+    which is raised by the "trigger" function mentioned above.
+ Notes on usage:
+ - Annotated code works well together with unannotated code:
+ Unannotated calls simply do not show up at all in the backtrace.
+ - It is not a good idea to let modules that were annotated during
+ different sessions run at the same time.  This is because the compiler
+ chooses small integers to identify individual functions, and there
+ will be clashes if different modules were compiled in separate sessions.
+ (Nothing will crash, and you will even be told about the clashes, but
+ back-trace information will in general not be useful.)
+ - Back-tracing can be confused by callcc and capture.
+ - The only way of getting a back-trace right now is to explicitly
+ invoke the "trigger" function from your user program.  Eventually, we
+ should make every exception carry back-trace information (if
+ available).  But since this creates more overhead at "raise"-time
+ (similar to the current exnHistory overhead), I have not yet
+ implemented this.  (The implementation will be rather easy.)  With
+ exceptions carrying back-trace information, this facility will be even
+ more useful because users don't need to modify their programs...
+ - While it is possible to compile the compiler with back-trace
+ annotations turned on (I did it to get some confidence in
+ correctness), you must make absolutely sure that core.sml and
+ btimp.sml are compiled WITHOUT annotation!  (core.sml cannot actually
+ be compiled with annotation because there is no core access yet, but
+ if you compile btimp.sml with annotation, then the system will go into
+ an infinite recursion and crash.)
+ Since CM currently does not know about BTrace, the only way to turn
+ annotations on and off for different modules of the compiler is to
+ interrupt CMB.make, change the settings, and re-invoke it.  Of course,
+ this is awkward and clumsy.
+ Sample sessions:
+ Standard ML of New Jersey v110.28.1 [FLINT v1.5], June 5, 2000
+ - SMLofNJ.Internals.BTrace.mode (SOME true);
+ [autoloading]
+ [autoloading done]
+ val it = false : bool
+ - structure X = struct
+ -     fun main n = let
+ -         fun a (x, 0) = d x
+ -           | a (x, n) = b (x, n - 1)
+ -         and b (x, n) = c (x, n)
+ -         and c (x, n) = a (x, n)
+ -         and d x = e (x, 3)
+ -         and e (x, 0) = f x
+ -           | e (x, n) = e (x, n - 1)
+ -         and f 0 = SMLofNJ.Internals.BTrace.trigger ()
+ -           | f n = n * g (n - 1)
+ -         and g n = a (n, 3)
+ -     in
+ -         f n
+ -     end
+ - end;
+ structure X : sig val main : int -> int end
+ - X.main 3;
+ *** BACK-TRACE ***
+ GOTO   stdIn:4.2-13.20: X.main[2].f
+ GOTO-( stdIn:4.2-13.20: X.main[2].e
+ GOTO   stdIn:4.2-13.20: X.main[2].d
+      / stdIn:4.2-13.20: X.main[2].a
+      | stdIn:4.2-13.20: X.main[2].b
+ GOTO-\ stdIn:4.2-13.20: X.main[2].c
+ CALL   stdIn:4.2-13.20: X.main[2].g
+ GOTO   stdIn:4.2-13.20: X.main[2].f
+ GOTO-( stdIn:4.2-13.20: X.main[2].e
+ GOTO   stdIn:4.2-13.20: X.main[2].d
+      / stdIn:4.2-13.20: X.main[2].a
+      | stdIn:4.2-13.20: X.main[2].b
+ GOTO-\ stdIn:4.2-13.20: X.main[2].c
+ CALL   stdIn:4.2-13.20: X.main[2].g
+ GOTO   stdIn:4.2-13.20: X.main[2].f
+ GOTO-( stdIn:4.2-13.20: X.main[2].e
+ GOTO   stdIn:4.2-13.20: X.main[2].d
+      / stdIn:4.2-13.20: X.main[2].a
+      | stdIn:4.2-13.20: X.main[2].b
+ GOTO-\ stdIn:4.2-13.20: X.main[2].c
+ CALL   stdIn:4.2-13.20: X.main[2].g
+ GOTO   stdIn:4.2-13.20: X.main[2].f
+ CALL   stdIn:2.15-17.4: X.main[2]
+ -
+ (Note that because of a FLINt bug the above code currently does not
+ compile without BTrace turned on.)
+ Here is another example, using my modified Tiger compiler:
+ Standard ML of New Jersey v110.28.1 [FLINT v1.5], June 5, 2000
+ - SMLofNJ.Internals.BTrace.mode (SOME true);
+ [autoloading]
+ [autoloading done]
+ val it = false : bool
+ - CM.make "sources.cm";
+ [autoloading]
+ ...
+ [autoloading done]
+ [scanning sources.cm]
+ [parsing (sources.cm):parse.sml]
+ [creating directory CM/SKEL ...]
+ [parsing (sources.cm):tiger.lex.sml]
+ ...
+ [wrote CM/sparc-unix/semant.sml]
+ [compiling (sources.cm):main.sml]
+ [wrote CM/sparc-unix/main.sml]
+ [New bindings added.]
+ val it = true : bool
+ - Main.compile ("../testcases/merge.tig", "foo.out");
+ *** BACK-TRACE ***
+ CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trvar
+ CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
+ CALL   lib/semant.sml:289.3-295.22: SemantFun[2].transExp.trexp.check[2]
+ GOTO   lib/semant.sml:289.3-295.22: SemantFun[2].transExp.trexp.check[2]
+ CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
+ CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
+ CALL   lib/semant.sml:488.3-505.6: SemantFun[2].transDec.trdec[2].transBody[2]
+      / lib/semant.sml:411.65-543.8: SemantFun[2].transDec
+ CALL-\ lib/semant.sml:413.2-540.9: SemantFun[2].transDec.trdec[2]
+ CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
+ CALL   lib/semant.sml:8.52-558.4: SemantFun[2].transProg[2]
+ CALL   main.sml:1.18-118.4: Main.compile[2]
+ -
+ ----------------------------------------------------------------------
+ Name: Matthias Blumen
+ Date: 2000/06/21 18:00:00 JST
+ Tag: blume-20000621-manual
+ Description:
+ CM manual update: Path environments documented.
+ ----------------------------------------------------------------------
+ Name: Matthias Blume
+ Date: 2000/06/19 13:40:00
+ Tag: blume-20000619-manual
+ Description:
+ CM manual and system/README update.  This only covers the fact that
+ there are no more implicit anchors.  (Path environments and the "bind"
+ option to "cm" have yet to be documented.)
+ ----------------------------------------------------------------------
+ Name: Matthias Blume
+ Date: 2000/06/19 11:05:00 JST
+ Tag: blume-20000619-chdir-bugfix
+ Description:
+ Fixed a bug in new SrcPath module that sometimes led to a bad chDir call.
+ ----------------------------------------------------------------------
+ Name: Matthias Blume
+ Date: 2000/06/18 22:00:10 JST
+ Tag: blume-20000618-implicit-anchors-really-gone
+ Description:
+ I updates the previous HISTORY entry where I forgot to mention that
+ implicit anchors are no longer with us.
+ The current update also gets rid of the (now useless) controller
+ CM.Control.implicit_anchors.
+ ----------------------------------------------------------------------
+ Name: Matthias Blume
+ Date: 2000/06/16 17:30:00 JST
+ Tag: blume-20000616-anchorenv
+ Description:
+ This patch implements the long anticipated (just kidding :) "anchor
+ environment" mechanism.  In the course of doing this, I also
+ re-implemented CM's internal "SrcPath" module from scratch.  The new
+ one should be more robust in certain boundary cases.  In any case, it
+ is a lot cleaner than its predecessor (IMHO).
+ This time, although there is yet another boot file format change, I
+ kept the unpickler backward-compatible.  As a result, no new bootfiles
+ are necessary and bootstrapping is straightforward.  (You cannot read
+ new bootfiles into an old system, but the other way around is no
+ problem.)
+ Visible changes:
+ ** 0. Implicit path anchors (without the leading $-symbol) are no
+ longer recognized at all. This means that such path names are not
+ illegal either.  For example, the name basis.cm simply refers to a
+ local file called "basis.cm" (i.e, the name is an ordinary path
+ relative to .cm-files directory).  Or, to put it differently, only
+ names that start with $ are anchored paths.
+ ** 1. The $<singlearc> abbreviation for $/<singlearc> has finally
+ vanished.
+ John (Reppy) had critizised this as soon as I originally proposed and
+ implemented it, but at that time I did not really deeply believe
+ him. :) Now I came full-circle because I need the $<singlearc> syntax
+ in another place where it cannot be seen as an abbreviation for
+ $/<singlearc>.  To avoid the confusion, $<singlearc> now means what it
+ seems to mean (i.e., it "expands" into the corresponding anchor
+ value).
+ However, when paths are used as members in CM description files, it
+ continues to be true that there must be at least another arc after the
+ anchor.  This is now enforced separately during semantic analysis
+ (i.e., from a lexical/syntactical point of view, the notation is ok.)
+ ** 2. The "cm" class now accepts an option "bind".  The option's value
+ is a sub-option list of precisely two items -- one labeled "anchor"
+ and the other one labeled "value".  As you might expect, "anchor" is
+ used to specify an anchor name to be bound, and "value" specifies what
+ the anchor is being bound to.
+ The value must be a directory name and can be given in either standard
+ syntax (including the possibility that it is itself an anchored path)
+ or native syntax.
+ Examples:
+    foo.cm (bind:(anchor:bar value:$mystuff/bar))
+    lib.cm (bind:(anchor:a value:"H:\\x\\y\\z"))  (* only works under windows *)
+ and so on.
+ The meaning of this is that the .cm-file will be processed with an
+ augmented anchor environment where the given anchor(s) is/are bound to
+ the given values(s).
+ The rationale for having this feature is this: Suppose you are trying
+ to use two different (already stable) libraries a.cm and b.cm (that
+ you perhaps didn't write yourself).  Further, suppose each of these
+ two libraries internally uses its own auxiliary library $aux/lib.cm.
+ Normally you would now have a problem because the anchor "lib" can not
+ be bound to more than one value globally.  Therefore, the project that
+ uses both a.cm and b.cm must locally redirect the anchor to some other
+ place:
+    a.cm (bind:(anchor:lib value:/usr/lib/smlnj/a-stuff))
+    b.cm (bind:(anchor:lib value:/usr/lib/smlnj/b-stuff))
+ This hard-wires $lib/aux.cm to /usr/lib/smlnj/a-stuff/aux.cm or
+ /usr/lib/smlnj/b-stuff/aux.cm, respectively.
+ Hard-wiring path names is a bit inflexible (and CM will verbosely warn
+ you when you do so at the time of CM.stabilize).  Therefore, you can
+ also use an anchored path as the value:
+   a.cm (bind:(anchor:lib value:$a-lib))
+   b.cm (bind:(anchor:lib value:$b-lib))
+ Now you can globally configure (using the usual CM.Anchor.anchor or
+ pathconfig machinery) bindings for "a-lib" and "b-lib".  Since "lib"
+ itself is always locally bound, setting it globally is no longer
+ meaningful or necessary (but it does not hurt either).  In fact, "lib"
+ can still be used as a global anchor for separate purposes.  As a
+ matter of fact, one can locally define "lib" in terms of a global
+ "lib":
+   a.cm (bind:(anchor:lib value:$lib/a))
+   b.cm (bind:(anchor:lib value:$lib/b))
+ ** 3: The encoding of path names has changed.  This affects the way
+ path names are shown in CM's progress report and also the internal
+ protocol encoding used for parallel make.
+ The encoding now uses one or more ':'-separated segments.  Each
+ segments corresponds to a file that has been specified relative to the
+ file given by its preceding segment.  The first segment is either
+ relative to the CWD, absolute, or anchored.  Each segment itself is
+ basically a Unix pathname; all segments but the first are relative.
+ Example:
+    $foo/bar/baz.cm:a/b/c.sml
+ This path denotes the file bar/a/b/c.sml relative to the directory
+ denoted by anchor "foo".  Notice that the encoding also includes
+ baz.cm which is the .cm-file that listed a/b/c.sml.  As usual, such
+ paths are resolved relative to the .cm-files directory, so baz.cm must
+ be ignored to get the "real" pathname.
+ To make this fact more obvious, CM puts the names of such "virtual
+ arcs" into parentheses when they appear in progress reports. (No
+ parentheses will appear in the internal protocol encoding.)  Thus,
+ what you really see is:
+   $foo/bar/(baz.cm):a/b/c.sml
+ I find this notation to be much more informative than before.
+ Another new feature of the encoding is that special characters
+ including parentheses, colons, (back)slashes, and white space are
+ written as \ddd (where ddd is the decimal encoding of the character).
+ *** The CM manual still needs to be updated.
+ ----------------------------------------------------------------------
+ Name: Allen Leung
+ Date: 2000/06/15 00:38:00
+ Tag: leunga-20000615-x86-peephole
+ x86 Peephole fix by Fermin.  Affects c-- and moby only.
+ ----------------------------------------------------------------------
+ Name: Matthias Blume
+ Date: 2000/06/12 11:40:00
+ Tag: blume-20000612-parmakefix
+ Description:
+ More cleanup after changing the file naming scheme: This time I
+ repaired the parallel make mechanism for CMB.make which I broke earlier.
+ ----------------------------------------------------------------------
+ Name: Allen Leung
+ Date: 2000/06/09 01:25:00
+ Tag: leunga-20000609-various
+ None of these things should affect normal SML/NJ operations
+. Peephole improvements provided by Fermin (c--)
+. New annotation DEFUSE for adding extra dependence (moby)
+. New X86 LOCK instructions (moby)
+. New machine description language for reservation tables (scheduling)
+. Fixes to various optimization/analysis modules (branch chaining, dominator
+    trees etc.)
+. I've changed the CM files so that they can work with versions
+.0.6, 110.25 and 110.28
+ ----------------------------------------------------------------------
  Name: Matthias Blume
  Date: 2000/06/09 12:40:00
  Tag: blume-20000609-log
-Line 574
+Line 1270
 .  Assembly
-     When generating assemby, resolve the value of client defined constants,
+     When generating assembly, resolve the value of client defined constants,
      instead of generating symbolic values.  This is controlled by the
      new flag "asm-resolve-constants", which is default to true.
-Line 597
+Line 1293
  To this end, I arranged that instead of "structure Core" as "structure
  _Core" is bound in the pervasive environment.  Core access is done via
- _Core (which can never be accidentially rebound because _Core is not a
+ _Core (which can never be accidentally rebound because _Core is not a
  legal surface-syntax symbol).
  The current solution is much cleaner because the core environment is
-Line 607
+Line 1303
  with dynamic and symbolic parts of the core environment.
  Remaining hackery (to bind the "magic" symbol _Core) is localized in the
- compilation mananger's bootstrap compiler (actually: in the "init group"
+ compilation manager's bootstrap compiler (actually: in the "init group"
  handling).  See the comments in src/system/smlnj/init/init.cmi for
  more details.
-Line 722
+Line 1418
     (specified in the .cm file at each instance where the tool's class is
     used).
-    This was done to accomodate the new "make" and "shell" tools which
+    This was done to accommodate the new "make" and "shell" tools which
-    facilitate fairly seemless hookup to portions of code managed using
+    facilitate fairly seamless hookup to portions of code managed using
     Makefiles or Shell scripts.
     There are no classes "shared" or "private" anymore.  Instead, the
-Line 735
+Line 1431
     All existing tools are described in the CM manual.
-    - Slightly better error handling.  (CM now surpresses many followup
+    - Slightly better error handling.  (CM now suppresses many followup
     error messages that tended to be more annoying than helpful.)
 . Major changes to the compiler's static environment data structures.
-Line 869
+Line 1565
       I've changed andl to testl in the floating point test sequence
       whenever appropriate.  The Intel optimization guide states that
-      testl is perferable to andl.
+      testl is preferable to andl.
 . RA (x86 only)
-Line 1051
+Line 1747
 . Tools.registerStdShellCmdTool (from smlnj/cm/tool.cm) takes an
  additional argument called "template" which is an optional string that
- specifiel the layout of the tool command line.  See the CM manual for
+ specifies the layout of the tool command line.  See the CM manual for
  explanation.
-. A special-purpose tool can be "regisitered" by simply dropping the
+. A special-purpose tool can be "registered" by simply dropping the
  corresponding <...>-tool.cm (and/or <...>-ext.cm) into the same
  directory where the .cm file lives that uses this tool.  (The
  behavior/misfeature until now was to look for the tool description
-Line 1098
+Line 1794
  rebuild.  Having sets of the form <base><k>.{bin,boot}.<arch>-unix for
  <k>=1,2,... is normally not a good idea when invoking fixpt.  However,
  they might be the result of an earlier partial run of fixpt (which
- perhaps got accidentially killed).  In this case, fixpt will quickly
+ perhaps got accidentally killed).  In this case, fixpt will quickly
  move through what exists before continuing where it left off earlier,
  and, thus, saves a lot of time.
-Line 1148
+Line 1844
    it from that remote directory.
    This should simplify installation further:  For machines that have
    access to the internet, just fetch <version>-config.tgz, unpack it,
-   edit config/targets, and go (run config/install.sh).  The scipt will
+   edit config/targets, and go (run config/install.sh).  The script will
    fetch everything else that it might need all by itself.
    For CVS users, this mechanism is not relevant for source archives, but

 Legend:



Removed from v.656
 


changed lines


 
Added in v.695
 Legend:



Removed from v.656
 


changed lines


 
Added in v.695
-Removed from v.656
+Added in v.695

root@smlnj-gforge.cs.uchicago.edu	ViewVC Help
Powered by ViewVC 1.0.0