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

SCM Repository

[smlnj] Diff of /sml/trunk/HISTORY
ViewVC logotype

Diff of /sml/trunk/HISTORY

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 644, Fri May 12 09:18:31 2000 UTC revision 682, Tue Jul 4 06:25:51 2000 UTC
# Line 13  Line 13 
13  Description:  Description:
14  ----------------------------------------------------------------------  ----------------------------------------------------------------------
15  Name: Matthias Blume  Name: Matthias Blume
16    Date: 2000/07/04 15:26:00
17    Tag: blume-20000704-trigger
18    Description:
20    1. Improvements to CM manual.
21    2. SMLofNJ.Internals.BTrace.trigger reinstated as an alternative way
22       of getting a back-trace.  The function, when called, raises an
23       internal exception which explicitly carries the full back-trace history,
24       so it is unaffected by any intervening handle-raise pairs ("trivial"
25       or not).  The interactive loop will print that history once it arrives
26       at top level.
27       Short of having all exceptions implicitly carry the full history, the
28       recommended way of using this facility is:
29         - compile your program with instrumentation "on"
30         - run it, when it raises an exception, look at the history
31         - if the history is "cut off" because of some handler, go and modify
32           your program so that it explicitly calls BTrace.trigger
33         - recompile (still instrumented), and rerun; look at the full history
35    ----------------------------------------------------------------------
36    Name: Matthias Blume
37    Date: 2000/07/03 15:36:00 JST
38    Tag: blume-20000702-manual
39    Description:
41    Small corrections and updates to CM manual.
43    ----------------------------------------------------------------------
44    Name: Matthias Blume
45    Date: 2000/06/29 16:04:00 JST
46    Tag: blume-20000629-yacctool
47    Description:
49    Changes:
51    1. Class "mlyacc" now takes separate arguments to pass options to
52       generated .sml- and .sig-files independently.
53    2. Corresponding CM manual updates.
54    3. BTrace module now also reports call sites.  (However, for loop clusters
55       it only shows from where the cluster was entered.)  There are associated
56       modifications to core.sml, internals.{sig,sml}, btrace.sml, and btimp.sml.
58    ----------------------------------------------------------------------
59    Name: Matthias Blume
60    Date: 2000/06/27 16:51:00 JST
61    Tag: blume-20000627-noweb
62    Description:
64    Changes:
66     1. Implemented "subdir" and "witness" options for noweb tool.
67        This caused some slight internal changes in CM's tool implementation.
68     2. Fixed bug in "tool plugin" mechanism.  This is essentially cleaning
69        some remaining issues from earlier path anchor changes.
70     3. Updated CM manual accordingly.
72     4. Changed implementation of back-tracing so that I now consider it
73        ready for prime-time.
75        In particular, you don't have to explicitly trigger the back-trace
76        anymore.  Instead, if you are running BTrace-instrumented code and
77        there is an uncaught exception (regardless of whether or not it was
78        raised in instrumented code), the top-level evalloop will print
79        the back-trace.
81        Features:
83          - Instrumented and uninstrumented code work together seemlessly.
84            (Of course, uninstrumented code is never mentioned in actual
85             back-traces.)
87          - Asymptotic time- and space-complexity of instrumented code is
88            equal to that of uninstrumented code.  (This means that
89            tail-recursion is preserved by the instrumentation phase.)
91          - Modules whose code has been instrumented in different sessions
92            work together without problem.
94          - There is no penalty whatsoever on uninstrumented code.
96          - There is no penalty on "raise" expressions, even in
97            instrumented code.
99        A potential bug (or perhaps it is a feature, too):
101          A back-trace reaches no further than the outermost instrumented
102          non-trivial "raise".  Here, a "trivial" raise is one that is the
103          sole RHS of a "handle" rule.  Thus, back-traces reach trough
105               <exp> handle e => raise e
107          and even
109               <exp> handle Foo => raise Bar
111          and, of course, through
113               <exp> handle Foo => ...
115         if the exception was not Foo.
117         Back-traces always reach right through any un-instrumented code
118         including any of its "handle" expressions, trivial or not.
120       To try this out, do the following:
122         - Erase all existing binfiles for your program.
123           (You may keep binfiles for those modules where you think you
124            definitely don't need back-tracing.)
125         - Turn on back-trace instrumentation:
126              SMLofNJ.Internals.BTrace.mode (SOME true);
127         - Recompile your program.  (I.e., run "CM.make" or "use".)
128         - You may now turn instrumentation off again (if you want):
129              SMLofNJ.Internals.BTrace.mode (SOME false);
130         - Run your program as usual.  If it raises an exception that
131           reaches the interactive toplevel, then a back-trace will
132           automatically be printed.  After that, the toplevel loop
133           will print the exception history as usual.
135    ----------------------------------------------------------------------
136    Name: Matthias Blume
137    Date: 2000/06/26 09:56:46 JST
138    Tag: blume-20000626-setup
139    Description:
141    CM: - setup-parameter to "sml" added; this can be used to run arbitrary
142          ML code before and after compiling a file (e.g., to set compiler
143          flags)
145    Compiler: - improved btrace API (in core.sml, internals.{sig,sml})
146              - associated changes to btrace.sml (BTrace instrumentation pass)
147              - cleaner implementation of btimp.sml (BTrace tracing and report
148                module)
150    CM manual: * new path encoding documented
151               * description of setup-parameter to "sml" added
153    The biggest user-visible change to back-tracing is that it is no
154    longer necessary to compile all traced modules within the same
155    session.  (This was a real limitation.)
157    ----------------------------------------------------------------------
158    Name: Matthias Blume
159    Date: 2000/06/24 12:40:00 JST
160    Tag: blume-20000624-startup
161    Description:
163    Fixes startup slowdown problem.  (I was calling SrcPath.sync a _tad_
164    bit too often -- to put it mildly. :)
166    ----------------------------------------------------------------------
167    Name: Matthias Blume
168    Date: 2000/06/23 18:20:00 JST
169    Tag: blume-20000623-btrace
170    Description:
172    This updates adds a backtrace facility to aid programmers in debugging
173    their programs.  This involves the following changes:
175    1. Module system/smlnj/init/core.sml (structure _Core) now has hooks for
176       keeping track of the current call stack.  When programs are compiled
177       in a special mode, the compiler will insert calls to these hooks
178       into the user program.
179       "Hook" means that it is possible for different implementations of
180       back-tracing to register themselves (at different times).
182    2. compiler/MiscUtil/profile/btrace.sml implements the annotation phase
183       as an Absyn.dec->Absyn.dec rewrite.  Normally this phase is turned off.
184       It can be turned on using this call:
185         SMLofNJ.Internals.BTrace.mode (SOME true);
186       Turning it off again:
187         SMLofNJ.Internals.BTrace.mode (SOME false);
188       Querying the current status:
189         SMLofNJ.Internals.BTrace.mode NONE;
190       Annotated programs are about twice as big as normal ones, and they
191       run a factor of 2 to 4 slower with a dummy back-trace plugin (one
192       where all hooks do nothing).  The slowdown with a plugin that is
193       actually useful (such as the one supplied by default) is even greater,
194       but in the case of the default plugin it is still only an constant
195       factor (amortized).
197    3. system/Basis/Implementation/NJ/internals.{sig,sml} have been augmented
198       with a sub-structure BTrace for controlling back-tracing.  In particular,
199       the above-mentioned function "mode" controls whether the annotation
200       phase is invoked by the compiler.  Another important function is
201       "trigger": when called it aborts the current execution and causes
202       the top-level loop to print a full back-trace.
204    4. compiler/MiscUtil/profile/btimp.sml is the current default plugin
205       for back-tracing.  It keeps track of the dynamic call stack and in
206       addition to that it keeps a partial history at each "level" of that
207       stack.  For example, if a tail-calls b, b tail-calls c, and c tail-calls
208       d and b (at separate times, dynamically), then the report will show:
210       GOTO   d
211             /c
212       GOTO  \b
213       CALL   a
215       This shows that there was an initial non-tail call of a, then a
216       tail-call to b or c, looping behavior in a cluster of functions that
217       consist of b and c, and then a goto from that cluster (i.e., either from
218       b or from c) to d.
220       Note that (depending on the user program) the amount of information
221       that the back-trace module has to keep track of at each level is bounded
222       by a constant.  Thus, the whole implementation has the same asymptotical
223       complexity as the original program (both in space and in time).
225    5. compiler/TopLevel/interact/evalloop.sml has been modified to
226       handle the special exception SMLofNJ.Internals.BTrace.BTrace
227       which is raised by the "trigger" function mentioned above.
229    Notes on usage:
231    - Annotated code works well together with unannotated code:
232    Unannotated calls simply do not show up at all in the backtrace.
234    - It is not a good idea to let modules that were annotated during
235    different sessions run at the same time.  This is because the compiler
236    chooses small integers to identify individual functions, and there
237    will be clashes if different modules were compiled in separate sessions.
238    (Nothing will crash, and you will even be told about the clashes, but
239    back-trace information will in general not be useful.)
241    - Back-tracing can be confused by callcc and capture.
243    - The only way of getting a back-trace right now is to explicitly
244    invoke the "trigger" function from your user program.  Eventually, we
245    should make every exception carry back-trace information (if
246    available).  But since this creates more overhead at "raise"-time
247    (similar to the current exnHistory overhead), I have not yet
248    implemented this.  (The implementation will be rather easy.)  With
249    exceptions carrying back-trace information, this facility will be even
250    more useful because users don't need to modify their programs...
252    - While it is possible to compile the compiler with back-trace
253    annotations turned on (I did it to get some confidence in
254    correctness), you must make absolutely sure that core.sml and
255    btimp.sml are compiled WITHOUT annotation!  (core.sml cannot actually
256    be compiled with annotation because there is no core access yet, but
257    if you compile btimp.sml with annotation, then the system will go into
258    an infinite recursion and crash.)
259    Since CM currently does not know about BTrace, the only way to turn
260    annotations on and off for different modules of the compiler is to
261    interrupt CMB.make, change the settings, and re-invoke it.  Of course,
262    this is awkward and clumsy.
264    Sample sessions:
266    Standard ML of New Jersey v110.28.1 [FLINT v1.5], June 5, 2000
267    - SMLofNJ.Internals.BTrace.mode (SOME true);
268    [autoloading]
269    [autoloading done]
270    val it = false : bool
271    - structure X = struct
272    -     fun main n = let
273    -         fun a (x, 0) = d x
274    -           | a (x, n) = b (x, n - 1)
275    -         and b (x, n) = c (x, n)
276    -         and c (x, n) = a (x, n)
277    -         and d x = e (x, 3)
278    -         and e (x, 0) = f x
279    -           | e (x, n) = e (x, n - 1)
280    -         and f 0 = SMLofNJ.Internals.BTrace.trigger ()
281    -           | f n = n * g (n - 1)
282    -         and g n = a (n, 3)
283    -     in
284    -         f n
285    -     end
286    - end;
287    structure X : sig val main : int -> int end
288    - X.main 3;
289    *** BACK-TRACE ***
290    GOTO   stdIn:4.2-13.20: X.main[2].f
291    GOTO-( stdIn:4.2-13.20: X.main[2].e
292    GOTO   stdIn:4.2-13.20: X.main[2].d
293         / stdIn:4.2-13.20: X.main[2].a
294         | stdIn:4.2-13.20: X.main[2].b
295    GOTO-\ stdIn:4.2-13.20: X.main[2].c
296    CALL   stdIn:4.2-13.20: X.main[2].g
297    GOTO   stdIn:4.2-13.20: X.main[2].f
298    GOTO-( stdIn:4.2-13.20: X.main[2].e
299    GOTO   stdIn:4.2-13.20: X.main[2].d
300         / stdIn:4.2-13.20: X.main[2].a
301         | stdIn:4.2-13.20: X.main[2].b
302    GOTO-\ stdIn:4.2-13.20: X.main[2].c
303    CALL   stdIn:4.2-13.20: X.main[2].g
304    GOTO   stdIn:4.2-13.20: X.main[2].f
305    GOTO-( stdIn:4.2-13.20: X.main[2].e
306    GOTO   stdIn:4.2-13.20: X.main[2].d
307         / stdIn:4.2-13.20: X.main[2].a
308         | stdIn:4.2-13.20: X.main[2].b
309    GOTO-\ stdIn:4.2-13.20: X.main[2].c
310    CALL   stdIn:4.2-13.20: X.main[2].g
311    GOTO   stdIn:4.2-13.20: X.main[2].f
312    CALL   stdIn:2.15-17.4: X.main[2]
313    -
315    (Note that because of a FLINt bug the above code currently does not
316    compile without BTrace turned on.)
318    Here is another example, using my modified Tiger compiler:
320    Standard ML of New Jersey v110.28.1 [FLINT v1.5], June 5, 2000
321    - SMLofNJ.Internals.BTrace.mode (SOME true);
322    [autoloading]
323    [autoloading done]
324    val it = false : bool
325    - CM.make "sources.cm";
326    [autoloading]
327    ...
328    [autoloading done]
329    [scanning sources.cm]
330    [parsing (sources.cm):parse.sml]
331    [creating directory CM/SKEL ...]
332    [parsing (sources.cm):tiger.lex.sml]
333    ...
334    [wrote CM/sparc-unix/semant.sml]
335    [compiling (sources.cm):main.sml]
336    [wrote CM/sparc-unix/main.sml]
337    [New bindings added.]
338    val it = true : bool
339    - Main.compile ("../testcases/merge.tig", "foo.out");
340    *** BACK-TRACE ***
341    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trvar
342    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
343    CALL   lib/semant.sml:289.3-295.22: SemantFun[2].transExp.trexp.check[2]
344    GOTO   lib/semant.sml:289.3-295.22: SemantFun[2].transExp.trexp.check[2]
345    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
346    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
347    CALL   lib/semant.sml:488.3-505.6: SemantFun[2].transDec.trdec[2].transBody[2]
348         / lib/semant.sml:411.65-543.8: SemantFun[2].transDec
349    CALL-\ lib/semant.sml:413.2-540.9: SemantFun[2].transDec.trdec[2]
350    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
351    CALL   lib/semant.sml:8.52-558.4: SemantFun[2].transProg[2]
352    CALL   main.sml:1.18-118.4: Main.compile[2]
353    -
355    ----------------------------------------------------------------------
356    Name: Matthias Blumen
357    Date: 2000/06/21 18:00:00 JST
358    Tag: blume-20000621-manual
359    Description:
361    CM manual update: Path environments documented.
363    ----------------------------------------------------------------------
364    Name: Matthias Blume
365    Date: 2000/06/19 13:40:00
366    Tag: blume-20000619-manual
367    Description:
369    CM manual and system/README update.  This only covers the fact that
370    there are no more implicit anchors.  (Path environments and the "bind"
371    option to "cm" have yet to be documented.)
373    ----------------------------------------------------------------------
374    Name: Matthias Blume
375    Date: 2000/06/19 11:05:00 JST
376    Tag: blume-20000619-chdir-bugfix
377    Description:
379    Fixed a bug in new SrcPath module that sometimes led to a bad chDir call.
381    ----------------------------------------------------------------------
382    Name: Matthias Blume
383    Date: 2000/06/18 22:00:10 JST
384    Tag: blume-20000618-implicit-anchors-really-gone
385    Description:
387    I updates the previous HISTORY entry where I forgot to mention that
388    implicit anchors are no longer with us.
390    The current update also gets rid of the (now useless) controller
391    CM.Control.implicit_anchors.
393    ----------------------------------------------------------------------
394    Name: Matthias Blume
395    Date: 2000/06/16 17:30:00 JST
396    Tag: blume-20000616-anchorenv
397    Description:
399    This patch implements the long anticipated (just kidding :) "anchor
400    environment" mechanism.  In the course of doing this, I also
401    re-implemented CM's internal "SrcPath" module from scratch.  The new
402    one should be more robust in certain boundary cases.  In any case, it
403    is a lot cleaner than its predecessor (IMHO).
405    This time, although there is yet another boot file format change, I
406    kept the unpickler backward-compatible.  As a result, no new bootfiles
407    are necessary and bootstrapping is straightforward.  (You cannot read
408    new bootfiles into an old system, but the other way around is no
409    problem.)
411    Visible changes:
413    ** 0. Implicit path anchors (without the leading $-symbol) are no
414    longer recognized at all. This means that such path names are not
415    illegal either.  For example, the name basis.cm simply refers to a
416    local file called "basis.cm" (i.e, the name is an ordinary path
417    relative to .cm-files directory).  Or, to put it differently, only
418    names that start with $ are anchored paths.
420    ** 1. The $<singlearc> abbreviation for $/<singlearc> has finally
421    vanished.
423    John (Reppy) had critizised this as soon as I originally proposed and
424    implemented it, but at that time I did not really deeply believe
425    him. :) Now I came full-circle because I need the $<singlearc> syntax
426    in another place where it cannot be seen as an abbreviation for
427    $/<singlearc>.  To avoid the confusion, $<singlearc> now means what it
428    seems to mean (i.e., it "expands" into the corresponding anchor
429    value).
431    However, when paths are used as members in CM description files, it
432    continues to be true that there must be at least another arc after the
433    anchor.  This is now enforced separately during semantic analysis
434    (i.e., from a lexical/syntactical point of view, the notation is ok.)
436    ** 2. The "cm" class now accepts an option "bind".  The option's value
437    is a sub-option list of precisely two items -- one labeled "anchor"
438    and the other one labeled "value".  As you might expect, "anchor" is
439    used to specify an anchor name to be bound, and "value" specifies what
440    the anchor is being bound to.
442    The value must be a directory name and can be given in either standard
443    syntax (including the possibility that it is itself an anchored path)
444    or native syntax.
446    Examples:
448       foo.cm (bind:(anchor:bar value:$mystuff/bar))
449       lib.cm (bind:(anchor:a value:"H:\\x\\y\\z"))  (* only works under windows *)
451    and so on.
453    The meaning of this is that the .cm-file will be processed with an
454    augmented anchor environment where the given anchor(s) is/are bound to
455    the given values(s).
457    The rationale for having this feature is this: Suppose you are trying
458    to use two different (already stable) libraries a.cm and b.cm (that
459    you perhaps didn't write yourself).  Further, suppose each of these
460    two libraries internally uses its own auxiliary library $aux/lib.cm.
461    Normally you would now have a problem because the anchor "lib" can not
462    be bound to more than one value globally.  Therefore, the project that
463    uses both a.cm and b.cm must locally redirect the anchor to some other
464    place:
466       a.cm (bind:(anchor:lib value:/usr/lib/smlnj/a-stuff))
467       b.cm (bind:(anchor:lib value:/usr/lib/smlnj/b-stuff))
469    This hard-wires $lib/aux.cm to /usr/lib/smlnj/a-stuff/aux.cm or
470    /usr/lib/smlnj/b-stuff/aux.cm, respectively.
472    Hard-wiring path names is a bit inflexible (and CM will verbosely warn
473    you when you do so at the time of CM.stabilize).  Therefore, you can
474    also use an anchored path as the value:
476      a.cm (bind:(anchor:lib value:$a-lib))
477      b.cm (bind:(anchor:lib value:$b-lib))
479    Now you can globally configure (using the usual CM.Anchor.anchor or
480    pathconfig machinery) bindings for "a-lib" and "b-lib".  Since "lib"
481    itself is always locally bound, setting it globally is no longer
482    meaningful or necessary (but it does not hurt either).  In fact, "lib"
483    can still be used as a global anchor for separate purposes.  As a
484    matter of fact, one can locally define "lib" in terms of a global
485    "lib":
487      a.cm (bind:(anchor:lib value:$lib/a))
488      b.cm (bind:(anchor:lib value:$lib/b))
490    ** 3: The encoding of path names has changed.  This affects the way
491    path names are shown in CM's progress report and also the internal
492    protocol encoding used for parallel make.
494    The encoding now uses one or more ':'-separated segments.  Each
495    segments corresponds to a file that has been specified relative to the
496    file given by its preceding segment.  The first segment is either
497    relative to the CWD, absolute, or anchored.  Each segment itself is
498    basically a Unix pathname; all segments but the first are relative.
500    Example:
502       $foo/bar/baz.cm:a/b/c.sml
504    This path denotes the file bar/a/b/c.sml relative to the directory
505    denoted by anchor "foo".  Notice that the encoding also includes
506    baz.cm which is the .cm-file that listed a/b/c.sml.  As usual, such
507    paths are resolved relative to the .cm-files directory, so baz.cm must
508    be ignored to get the "real" pathname.
510    To make this fact more obvious, CM puts the names of such "virtual
511    arcs" into parentheses when they appear in progress reports. (No
512    parentheses will appear in the internal protocol encoding.)  Thus,
513    what you really see is:
515      $foo/bar/(baz.cm):a/b/c.sml
517    I find this notation to be much more informative than before.
519    Another new feature of the encoding is that special characters
520    including parentheses, colons, (back)slashes, and white space are
521    written as \ddd (where ddd is the decimal encoding of the character).
523    *** The CM manual still needs to be updated.
525    ----------------------------------------------------------------------
526    Name: Allen Leung
527    Date: 2000/06/15 00:38:00
528    Tag: leunga-20000615-x86-peephole
530    x86 Peephole fix by Fermin.  Affects c-- and moby only.
532    ----------------------------------------------------------------------
533    Name: Matthias Blume
534    Date: 2000/06/12 11:40:00
535    Tag: blume-20000612-parmakefix
536    Description:
538    More cleanup after changing the file naming scheme: This time I
539    repaired the parallel make mechanism for CMB.make which I broke earlier.
541    ----------------------------------------------------------------------
542    Name: Allen Leung
543    Date: 2000/06/09 01:25:00
544    Tag: leunga-20000609-various
546    None of these things should affect normal SML/NJ operations
548    1. Peephole improvements provided by Fermin (c--)
549    2. New annotation DEFUSE for adding extra dependence (moby)
550    3. New X86 LOCK instructions (moby)
551    4. New machine description language for reservation tables (scheduling)
552    5. Fixes to various optimization/analysis modules (branch chaining, dominator
553       trees etc.)
554    6. I've changed the CM files so that they can work with versions
555       110.0.6, 110.25 and 110.28
557    ----------------------------------------------------------------------
558    Name: Matthias Blume
559    Date: 2000/06/09 12:40:00
560    Tag: blume-20000609-log
561    Description:
563    - Removed all(?) remaining RCS Log entries from sources.
565    - Fixed bug in ml-yacc and ml-lex sources (use explicit anchors for
566      anchored paths).
568    ----------------------------------------------------------------------
569    Name: Matthias Blume
570    Date: 2000/06/07 17:00:00 JST
571    Tag: blume-20000607-no-implicit-anchors
572    Description:
574    1. This update changes the default setting for
575    CM.Control.implicit_anchors from true to false.  This means that
576    implicit anchors are no longer permitted by default.  I also tried to
577    make sure that nothing else still relies on implicit anchors.
578    (This is the next step on the schedule towards a CM that does not even
579    have the notion of implicit anchors anymore.)
581    2. More CM manual updates.
583    3. I managed to track down and fix the pickling bug I mentioned last
584    time.  Because of the previously existing workaround, this entails no
585    immediate practical changes.
587    ----------------------------------------------------------------------
588    Name: Matthias Blume
589    Date: 2000/06/06 11:15:00 JST
590    Tag: blume-20000606-lazierpickle
591    Description:
593    !!!! NEW BOOT FILES !!!!
595    * The main purpose of this update is to make library pickles lazier in
596    order to reduce the initial space penalty for autoloading a library.
597    As a result, it is now possible to have $smlnj/compiler.cm
598    pre-registered.  This should take care of the many complaints or
599    inquiries about missing structure Compiler.  This required changes to
600    CM's internal data structures and small tweaks to some algorithms.
602    As a neat additional effect, it is no longer necessary (for the sake
603    of lean heap image files) to distinguish between a "minimal" CM and a
604    "full" CM.  Now, there is only one CM (i.e., the "full" version:
605    $smlnj/cm.cm aka $smlnj/cm/full.cm), and it is always available at the
606    interactive top level. ($smlnj/cm/minimal.cm is gone.)
608    To make the life of compiler-hackers easier, "makeml" now also
609    pre-registers $smlnj/cmb.cm (aka $smlnj/cmb/current.cm).  In other
610    words, after you bootstrap a new sml for the first time, you will not
611    have to autoload $smlnj/cmb.cm again afterwards.  (The first time
612    around you will still have to do it, though.)
614    * A second change consists of major updates to the CM manual.  There
615    are now several appendices with summary information and also a full
616    specification of the CM description file syntax.
618    * In directory src/system I added the script "allcross".  This script
619    invokes sml and cross-compiles the compiler for all supported
620    architectures.  (Useful when providing a new set of boot files.)
622    * There seems to be a latent bug in my "lazy pickles" mechanism.  I
623    added a small tweak to pickle-util.sml to work around this problem,
624    but it is not a proper fix yet.  I will investigate further.  (The
625    effect of the bug was an inflation of library pickle size.)
627    * Version number increased to 110.28.1 (to avoid compatibility problems).
629    ----------------------------------------------------------------------
630    Name: Allen Leung
631    Date: 2000/05/25 17:28 EDT
632    Tag: leunga-20000525-ra
633    Description:
635      Fixed a bug in freezing phase of the register allocator.
637    ----------------------------------------------------------------------
638    Name: Allen Leung
639    Date: 2000/05/15 22:53 EDT
640    Tag: leunga-20000515-alpha-x86-ra
641    Description:
643      1. Alpha
645          Slight cleanup.  Removed the instruction SGNXL
647      2. X86
649          Added the following instructions to the instruction set:
651            ROLx, RORx,
652            BTx, BTSx, BTLx, BTRx,
653            XCHGx, and variants with the LOCK prefix
655      3. Register Allocation
657          The module ra-rewrite-with-renaming has been improved.
659      These have no effect on SML/NJ.
661    ----------------------------------------------------------------------
662    Name: Matthias Blume
663    Date: 2000/05/15 16:20:00 JST
664    Tag: blume-20000515-lightrebuild
665    Description:
667    1. I added an alternative to "-rebuild" to "makeml".  The difference is
668       that prior to calling CMB.make' the CM-variable "LIGHT" will be
669       defined.  In effect, the command will not build any cross-compiler
670       backends and therefore finish more quickly.
672       The "fixpt" script also takes a "-light" switch to be able to use
673       this new facility while compiling for a fixpoint.
675    2. I replaced all mentions of anchored paths in group owner specifications
676       with simple relative paths (usually starting with "..").
677       The rationale is that a library's internal workings should not be
678       compromised by the lack of some anchor.  (An anchor is necessary
679       for someone who wants to refer to the library by an anchored path,
680       but it should not be necessary to build the same library in the first
681       place.)
683    3. I changed the way CM's tool mechanism determines the shell command
684       string used for things like ml-yacc etc. so that it does not break
685       when CM.Control.implicit_anchors is turned off.
687    ----------------------------------------------------------------------
688    Name: Matthias Blume
689  Date: 2000/05/12 18:20:00 JST  Date: 2000/05/12 18:20:00 JST
690  Tag: blume-20000512-ml-build  Tag: blume-20000512-ml-build
691  Description:  Description:
# Line 444  Line 1117 
1118  3.  Assembly  3.  Assembly
1120      When generating assemby, resolve the value of client defined constants,      When generating assembly, resolve the value of client defined constants,
1121      instead of generating symbolic values.  This is controlled by the      instead of generating symbolic values.  This is controlled by the
1122      new flag "asm-resolve-constants", which is default to true.      new flag "asm-resolve-constants", which is default to true.
# Line 467  Line 1140 
1141  To this end, I arranged that instead of "structure Core" as "structure  To this end, I arranged that instead of "structure Core" as "structure
1142  _Core" is bound in the pervasive environment.  Core access is done via  _Core" is bound in the pervasive environment.  Core access is done via
1143  _Core (which can never be accidentially rebound because _Core is not a  _Core (which can never be accidentally rebound because _Core is not a
1144  legal surface-syntax symbol).  legal surface-syntax symbol).
1146  The current solution is much cleaner because the core environment is  The current solution is much cleaner because the core environment is
# Line 477  Line 1150 
1150  with dynamic and symbolic parts of the core environment.  with dynamic and symbolic parts of the core environment.
1152  Remaining hackery (to bind the "magic" symbol _Core) is localized in the  Remaining hackery (to bind the "magic" symbol _Core) is localized in the
1153  compilation mananger's bootstrap compiler (actually: in the "init group"  compilation manager's bootstrap compiler (actually: in the "init group"
1154  handling).  See the comments in src/system/smlnj/init/init.cmi for  handling).  See the comments in src/system/smlnj/init/init.cmi for
1155  more details.  more details.
# Line 592  Line 1265 
1265     (specified in the .cm file at each instance where the tool's class is     (specified in the .cm file at each instance where the tool's class is
1266     used).     used).
1268     This was done to accomodate the new "make" and "shell" tools which     This was done to accommodate the new "make" and "shell" tools which
1269     facilitate fairly seemless hookup to portions of code managed using     facilitate fairly seamless hookup to portions of code managed using
1270     Makefiles or Shell scripts.     Makefiles or Shell scripts.
1272     There are no classes "shared" or "private" anymore.  Instead, the     There are no classes "shared" or "private" anymore.  Instead, the
# Line 605  Line 1278 
1279     All existing tools are described in the CM manual.     All existing tools are described in the CM manual.
1281     - Slightly better error handling.  (CM now surpresses many followup     - Slightly better error handling.  (CM now suppresses many followup
1282     error messages that tended to be more annoying than helpful.)     error messages that tended to be more annoying than helpful.)
1284  2. Major changes to the compiler's static environment data structures.  2. Major changes to the compiler's static environment data structures.
# Line 739  Line 1412 
1413       I've changed andl to testl in the floating point test sequence       I've changed andl to testl in the floating point test sequence
1414       whenever appropriate.  The Intel optimization guide states that       whenever appropriate.  The Intel optimization guide states that
1415       testl is perferable to andl.       testl is preferable to andl.
1417  7. RA (x86 only)  7. RA (x86 only)
# Line 921  Line 1594 
1595  1. Tools.registerStdShellCmdTool (from smlnj/cm/tool.cm) takes an  1. Tools.registerStdShellCmdTool (from smlnj/cm/tool.cm) takes an
1596  additional argument called "template" which is an optional string that  additional argument called "template" which is an optional string that
1597  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
1598  explanation.  explanation.
1600  2. A special-purpose tool can be "regisitered" by simply dropping the  2. A special-purpose tool can be "registered" by simply dropping the
1601  corresponding <...>-tool.cm (and/or <...>-ext.cm) into the same  corresponding <...>-tool.cm (and/or <...>-ext.cm) into the same
1602  directory where the .cm file lives that uses this tool.  (The  directory where the .cm file lives that uses this tool.  (The
1603  behavior/misfeature until now was to look for the tool description  behavior/misfeature until now was to look for the tool description
# Line 968  Line 1641 
1641  rebuild.  Having sets of the form <base><k>.{bin,boot}.<arch>-unix for  rebuild.  Having sets of the form <base><k>.{bin,boot}.<arch>-unix for
1642  <k>=1,2,... is normally not a good idea when invoking fixpt.  However,  <k>=1,2,... is normally not a good idea when invoking fixpt.  However,
1643  they might be the result of an earlier partial run of fixpt (which  they might be the result of an earlier partial run of fixpt (which
1644  perhaps got accidentially killed).  In this case, fixpt will quickly  perhaps got accidentally killed).  In this case, fixpt will quickly
1645  move through what exists before continuing where it left off earlier,  move through what exists before continuing where it left off earlier,
1646  and, thus, saves a lot of time.  and, thus, saves a lot of time.
# Line 1018  Line 1691 
1691    it from that remote directory.    it from that remote directory.
1692    This should simplify installation further:  For machines that have    This should simplify installation further:  For machines that have
1693    access to the internet, just fetch <version>-config.tgz, unpack it,    access to the internet, just fetch <version>-config.tgz, unpack it,
1694    edit config/targets, and go (run config/install.sh).  The scipt will    edit config/targets, and go (run config/install.sh).  The script will
1695    fetch everything else that it might need all by itself.    fetch everything else that it might need all by itself.
1697    For CVS users, this mechanism is not relevant for source archives, but    For CVS users, this mechanism is not relevant for source archives, but

Removed from v.644  
changed lines
  Added in v.682

ViewVC Help
Powered by ViewVC 1.0.0