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 652, Tue Jun 6 02:14:56 2000 UTC revision 683, Wed Jul 5 00:42:19 2000 UTC
# Line 12  Line 12 
12  Tag: <post-commit CVS tag>  Tag: <post-commit CVS tag>
13  Description:  Description:
14  ----------------------------------------------------------------------  ----------------------------------------------------------------------
15    Name: Allen Leung
16    Date: 2000/06/15 00:38:00
17    Tag: leunga-20000704-sparc-x86
19    1. x86 peephole improvement sp += k; sp -= k => nop  [from John]
20    2. fix to x86 RET bug [found by Dan Grossman]
21    3. sparc assembly bug fix for ticc instructions [found by Fermin]
23       Affects c-- and moby only
25    ----------------------------------------------------------------------
26    Name: Matthias Blume
27    Date: 2000/07/04 15:26:00
28    Tag: blume-20000704-trigger
29    Description:
31    1. Improvements to CM manual.
32    2. SMLofNJ.Internals.BTrace.trigger reinstated as an alternative way
33       of getting a back-trace.  The function, when called, raises an
34       internal exception which explicitly carries the full back-trace history,
35       so it is unaffected by any intervening handle-raise pairs ("trivial"
36       or not).  The interactive loop will print that history once it arrives
37       at top level.
38       Short of having all exceptions implicitly carry the full history, the
39       recommended way of using this facility is:
40         - compile your program with instrumentation "on"
41         - run it, when it raises an exception, look at the history
42         - if the history is "cut off" because of some handler, go and modify
43           your program so that it explicitly calls BTrace.trigger
44         - recompile (still instrumented), and rerun; look at the full history
46    ----------------------------------------------------------------------
47    Name: Matthias Blume
48    Date: 2000/07/03 15:36:00 JST
49    Tag: blume-20000702-manual
50    Description:
52    Small corrections and updates to CM manual.
54    ----------------------------------------------------------------------
55    Name: Matthias Blume
56    Date: 2000/06/29 16:04:00 JST
57    Tag: blume-20000629-yacctool
58    Description:
60    Changes:
62    1. Class "mlyacc" now takes separate arguments to pass options to
63       generated .sml- and .sig-files independently.
64    2. Corresponding CM manual updates.
65    3. BTrace module now also reports call sites.  (However, for loop clusters
66       it only shows from where the cluster was entered.)  There are associated
67       modifications to core.sml, internals.{sig,sml}, btrace.sml, and btimp.sml.
69    ----------------------------------------------------------------------
70    Name: Matthias Blume
71    Date: 2000/06/27 16:51:00 JST
72    Tag: blume-20000627-noweb
73    Description:
75    Changes:
77     1. Implemented "subdir" and "witness" options for noweb tool.
78        This caused some slight internal changes in CM's tool implementation.
79     2. Fixed bug in "tool plugin" mechanism.  This is essentially cleaning
80        some remaining issues from earlier path anchor changes.
81     3. Updated CM manual accordingly.
83     4. Changed implementation of back-tracing so that I now consider it
84        ready for prime-time.
86        In particular, you don't have to explicitly trigger the back-trace
87        anymore.  Instead, if you are running BTrace-instrumented code and
88        there is an uncaught exception (regardless of whether or not it was
89        raised in instrumented code), the top-level evalloop will print
90        the back-trace.
92        Features:
94          - Instrumented and uninstrumented code work together seemlessly.
95            (Of course, uninstrumented code is never mentioned in actual
96             back-traces.)
98          - Asymptotic time- and space-complexity of instrumented code is
99            equal to that of uninstrumented code.  (This means that
100            tail-recursion is preserved by the instrumentation phase.)
102          - Modules whose code has been instrumented in different sessions
103            work together without problem.
105          - There is no penalty whatsoever on uninstrumented code.
107          - There is no penalty on "raise" expressions, even in
108            instrumented code.
110        A potential bug (or perhaps it is a feature, too):
112          A back-trace reaches no further than the outermost instrumented
113          non-trivial "raise".  Here, a "trivial" raise is one that is the
114          sole RHS of a "handle" rule.  Thus, back-traces reach trough
116               <exp> handle e => raise e
118          and even
120               <exp> handle Foo => raise Bar
122          and, of course, through
124               <exp> handle Foo => ...
126         if the exception was not Foo.
128         Back-traces always reach right through any un-instrumented code
129         including any of its "handle" expressions, trivial or not.
131       To try this out, do the following:
133         - Erase all existing binfiles for your program.
134           (You may keep binfiles for those modules where you think you
135            definitely don't need back-tracing.)
136         - Turn on back-trace instrumentation:
137              SMLofNJ.Internals.BTrace.mode (SOME true);
138         - Recompile your program.  (I.e., run "CM.make" or "use".)
139         - You may now turn instrumentation off again (if you want):
140              SMLofNJ.Internals.BTrace.mode (SOME false);
141         - Run your program as usual.  If it raises an exception that
142           reaches the interactive toplevel, then a back-trace will
143           automatically be printed.  After that, the toplevel loop
144           will print the exception history as usual.
146    ----------------------------------------------------------------------
147    Name: Matthias Blume
148    Date: 2000/06/26 09:56:46 JST
149    Tag: blume-20000626-setup
150    Description:
152    CM: - setup-parameter to "sml" added; this can be used to run arbitrary
153          ML code before and after compiling a file (e.g., to set compiler
154          flags)
156    Compiler: - improved btrace API (in core.sml, internals.{sig,sml})
157              - associated changes to btrace.sml (BTrace instrumentation pass)
158              - cleaner implementation of btimp.sml (BTrace tracing and report
159                module)
161    CM manual: * new path encoding documented
162               * description of setup-parameter to "sml" added
164    The biggest user-visible change to back-tracing is that it is no
165    longer necessary to compile all traced modules within the same
166    session.  (This was a real limitation.)
168    ----------------------------------------------------------------------
169    Name: Matthias Blume
170    Date: 2000/06/24 12:40:00 JST
171    Tag: blume-20000624-startup
172    Description:
174    Fixes startup slowdown problem.  (I was calling SrcPath.sync a _tad_
175    bit too often -- to put it mildly. :)
177    ----------------------------------------------------------------------
178    Name: Matthias Blume
179    Date: 2000/06/23 18:20:00 JST
180    Tag: blume-20000623-btrace
181    Description:
183    This updates adds a backtrace facility to aid programmers in debugging
184    their programs.  This involves the following changes:
186    1. Module system/smlnj/init/core.sml (structure _Core) now has hooks for
187       keeping track of the current call stack.  When programs are compiled
188       in a special mode, the compiler will insert calls to these hooks
189       into the user program.
190       "Hook" means that it is possible for different implementations of
191       back-tracing to register themselves (at different times).
193    2. compiler/MiscUtil/profile/btrace.sml implements the annotation phase
194       as an Absyn.dec->Absyn.dec rewrite.  Normally this phase is turned off.
195       It can be turned on using this call:
196         SMLofNJ.Internals.BTrace.mode (SOME true);
197       Turning it off again:
198         SMLofNJ.Internals.BTrace.mode (SOME false);
199       Querying the current status:
200         SMLofNJ.Internals.BTrace.mode NONE;
201       Annotated programs are about twice as big as normal ones, and they
202       run a factor of 2 to 4 slower with a dummy back-trace plugin (one
203       where all hooks do nothing).  The slowdown with a plugin that is
204       actually useful (such as the one supplied by default) is even greater,
205       but in the case of the default plugin it is still only an constant
206       factor (amortized).
208    3. system/Basis/Implementation/NJ/internals.{sig,sml} have been augmented
209       with a sub-structure BTrace for controlling back-tracing.  In particular,
210       the above-mentioned function "mode" controls whether the annotation
211       phase is invoked by the compiler.  Another important function is
212       "trigger": when called it aborts the current execution and causes
213       the top-level loop to print a full back-trace.
215    4. compiler/MiscUtil/profile/btimp.sml is the current default plugin
216       for back-tracing.  It keeps track of the dynamic call stack and in
217       addition to that it keeps a partial history at each "level" of that
218       stack.  For example, if a tail-calls b, b tail-calls c, and c tail-calls
219       d and b (at separate times, dynamically), then the report will show:
221       GOTO   d
222             /c
223       GOTO  \b
224       CALL   a
226       This shows that there was an initial non-tail call of a, then a
227       tail-call to b or c, looping behavior in a cluster of functions that
228       consist of b and c, and then a goto from that cluster (i.e., either from
229       b or from c) to d.
231       Note that (depending on the user program) the amount of information
232       that the back-trace module has to keep track of at each level is bounded
233       by a constant.  Thus, the whole implementation has the same asymptotical
234       complexity as the original program (both in space and in time).
236    5. compiler/TopLevel/interact/evalloop.sml has been modified to
237       handle the special exception SMLofNJ.Internals.BTrace.BTrace
238       which is raised by the "trigger" function mentioned above.
240    Notes on usage:
242    - Annotated code works well together with unannotated code:
243    Unannotated calls simply do not show up at all in the backtrace.
245    - It is not a good idea to let modules that were annotated during
246    different sessions run at the same time.  This is because the compiler
247    chooses small integers to identify individual functions, and there
248    will be clashes if different modules were compiled in separate sessions.
249    (Nothing will crash, and you will even be told about the clashes, but
250    back-trace information will in general not be useful.)
252    - Back-tracing can be confused by callcc and capture.
254    - The only way of getting a back-trace right now is to explicitly
255    invoke the "trigger" function from your user program.  Eventually, we
256    should make every exception carry back-trace information (if
257    available).  But since this creates more overhead at "raise"-time
258    (similar to the current exnHistory overhead), I have not yet
259    implemented this.  (The implementation will be rather easy.)  With
260    exceptions carrying back-trace information, this facility will be even
261    more useful because users don't need to modify their programs...
263    - While it is possible to compile the compiler with back-trace
264    annotations turned on (I did it to get some confidence in
265    correctness), you must make absolutely sure that core.sml and
266    btimp.sml are compiled WITHOUT annotation!  (core.sml cannot actually
267    be compiled with annotation because there is no core access yet, but
268    if you compile btimp.sml with annotation, then the system will go into
269    an infinite recursion and crash.)
270    Since CM currently does not know about BTrace, the only way to turn
271    annotations on and off for different modules of the compiler is to
272    interrupt CMB.make, change the settings, and re-invoke it.  Of course,
273    this is awkward and clumsy.
275    Sample sessions:
277    Standard ML of New Jersey v110.28.1 [FLINT v1.5], June 5, 2000
278    - SMLofNJ.Internals.BTrace.mode (SOME true);
279    [autoloading]
280    [autoloading done]
281    val it = false : bool
282    - structure X = struct
283    -     fun main n = let
284    -         fun a (x, 0) = d x
285    -           | a (x, n) = b (x, n - 1)
286    -         and b (x, n) = c (x, n)
287    -         and c (x, n) = a (x, n)
288    -         and d x = e (x, 3)
289    -         and e (x, 0) = f x
290    -           | e (x, n) = e (x, n - 1)
291    -         and f 0 = SMLofNJ.Internals.BTrace.trigger ()
292    -           | f n = n * g (n - 1)
293    -         and g n = a (n, 3)
294    -     in
295    -         f n
296    -     end
297    - end;
298    structure X : sig val main : int -> int end
299    - X.main 3;
300    *** BACK-TRACE ***
301    GOTO   stdIn:4.2-13.20: X.main[2].f
302    GOTO-( stdIn:4.2-13.20: X.main[2].e
303    GOTO   stdIn:4.2-13.20: X.main[2].d
304         / stdIn:4.2-13.20: X.main[2].a
305         | stdIn:4.2-13.20: X.main[2].b
306    GOTO-\ stdIn:4.2-13.20: X.main[2].c
307    CALL   stdIn:4.2-13.20: X.main[2].g
308    GOTO   stdIn:4.2-13.20: X.main[2].f
309    GOTO-( stdIn:4.2-13.20: X.main[2].e
310    GOTO   stdIn:4.2-13.20: X.main[2].d
311         / stdIn:4.2-13.20: X.main[2].a
312         | stdIn:4.2-13.20: X.main[2].b
313    GOTO-\ stdIn:4.2-13.20: X.main[2].c
314    CALL   stdIn:4.2-13.20: X.main[2].g
315    GOTO   stdIn:4.2-13.20: X.main[2].f
316    GOTO-( stdIn:4.2-13.20: X.main[2].e
317    GOTO   stdIn:4.2-13.20: X.main[2].d
318         / stdIn:4.2-13.20: X.main[2].a
319         | stdIn:4.2-13.20: X.main[2].b
320    GOTO-\ stdIn:4.2-13.20: X.main[2].c
321    CALL   stdIn:4.2-13.20: X.main[2].g
322    GOTO   stdIn:4.2-13.20: X.main[2].f
323    CALL   stdIn:2.15-17.4: X.main[2]
324    -
326    (Note that because of a FLINt bug the above code currently does not
327    compile without BTrace turned on.)
329    Here is another example, using my modified Tiger compiler:
331    Standard ML of New Jersey v110.28.1 [FLINT v1.5], June 5, 2000
332    - SMLofNJ.Internals.BTrace.mode (SOME true);
333    [autoloading]
334    [autoloading done]
335    val it = false : bool
336    - CM.make "sources.cm";
337    [autoloading]
338    ...
339    [autoloading done]
340    [scanning sources.cm]
341    [parsing (sources.cm):parse.sml]
342    [creating directory CM/SKEL ...]
343    [parsing (sources.cm):tiger.lex.sml]
344    ...
345    [wrote CM/sparc-unix/semant.sml]
346    [compiling (sources.cm):main.sml]
347    [wrote CM/sparc-unix/main.sml]
348    [New bindings added.]
349    val it = true : bool
350    - Main.compile ("../testcases/merge.tig", "foo.out");
351    *** BACK-TRACE ***
352    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trvar
353    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
354    CALL   lib/semant.sml:289.3-295.22: SemantFun[2].transExp.trexp.check[2]
355    GOTO   lib/semant.sml:289.3-295.22: SemantFun[2].transExp.trexp.check[2]
356    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
357    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
358    CALL   lib/semant.sml:488.3-505.6: SemantFun[2].transDec.trdec[2].transBody[2]
359         / lib/semant.sml:411.65-543.8: SemantFun[2].transDec
360    CALL-\ lib/semant.sml:413.2-540.9: SemantFun[2].transDec.trdec[2]
361    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
362    CALL   lib/semant.sml:8.52-558.4: SemantFun[2].transProg[2]
363    CALL   main.sml:1.18-118.4: Main.compile[2]
364    -
366    ----------------------------------------------------------------------
367    Name: Matthias Blumen
368    Date: 2000/06/21 18:00:00 JST
369    Tag: blume-20000621-manual
370    Description:
372    CM manual update: Path environments documented.
374    ----------------------------------------------------------------------
375    Name: Matthias Blume
376    Date: 2000/06/19 13:40:00
377    Tag: blume-20000619-manual
378    Description:
380    CM manual and system/README update.  This only covers the fact that
381    there are no more implicit anchors.  (Path environments and the "bind"
382    option to "cm" have yet to be documented.)
384    ----------------------------------------------------------------------
385    Name: Matthias Blume
386    Date: 2000/06/19 11:05:00 JST
387    Tag: blume-20000619-chdir-bugfix
388    Description:
390    Fixed a bug in new SrcPath module that sometimes led to a bad chDir call.
392    ----------------------------------------------------------------------
393    Name: Matthias Blume
394    Date: 2000/06/18 22:00:10 JST
395    Tag: blume-20000618-implicit-anchors-really-gone
396    Description:
398    I updates the previous HISTORY entry where I forgot to mention that
399    implicit anchors are no longer with us.
401    The current update also gets rid of the (now useless) controller
402    CM.Control.implicit_anchors.
404    ----------------------------------------------------------------------
405    Name: Matthias Blume
406    Date: 2000/06/16 17:30:00 JST
407    Tag: blume-20000616-anchorenv
408    Description:
410    This patch implements the long anticipated (just kidding :) "anchor
411    environment" mechanism.  In the course of doing this, I also
412    re-implemented CM's internal "SrcPath" module from scratch.  The new
413    one should be more robust in certain boundary cases.  In any case, it
414    is a lot cleaner than its predecessor (IMHO).
416    This time, although there is yet another boot file format change, I
417    kept the unpickler backward-compatible.  As a result, no new bootfiles
418    are necessary and bootstrapping is straightforward.  (You cannot read
419    new bootfiles into an old system, but the other way around is no
420    problem.)
422    Visible changes:
424    ** 0. Implicit path anchors (without the leading $-symbol) are no
425    longer recognized at all. This means that such path names are not
426    illegal either.  For example, the name basis.cm simply refers to a
427    local file called "basis.cm" (i.e, the name is an ordinary path
428    relative to .cm-files directory).  Or, to put it differently, only
429    names that start with $ are anchored paths.
431    ** 1. The $<singlearc> abbreviation for $/<singlearc> has finally
432    vanished.
434    John (Reppy) had critizised this as soon as I originally proposed and
435    implemented it, but at that time I did not really deeply believe
436    him. :) Now I came full-circle because I need the $<singlearc> syntax
437    in another place where it cannot be seen as an abbreviation for
438    $/<singlearc>.  To avoid the confusion, $<singlearc> now means what it
439    seems to mean (i.e., it "expands" into the corresponding anchor
440    value).
442    However, when paths are used as members in CM description files, it
443    continues to be true that there must be at least another arc after the
444    anchor.  This is now enforced separately during semantic analysis
445    (i.e., from a lexical/syntactical point of view, the notation is ok.)
447    ** 2. The "cm" class now accepts an option "bind".  The option's value
448    is a sub-option list of precisely two items -- one labeled "anchor"
449    and the other one labeled "value".  As you might expect, "anchor" is
450    used to specify an anchor name to be bound, and "value" specifies what
451    the anchor is being bound to.
453    The value must be a directory name and can be given in either standard
454    syntax (including the possibility that it is itself an anchored path)
455    or native syntax.
457    Examples:
459       foo.cm (bind:(anchor:bar value:$mystuff/bar))
460       lib.cm (bind:(anchor:a value:"H:\\x\\y\\z"))  (* only works under windows *)
462    and so on.
464    The meaning of this is that the .cm-file will be processed with an
465    augmented anchor environment where the given anchor(s) is/are bound to
466    the given values(s).
468    The rationale for having this feature is this: Suppose you are trying
469    to use two different (already stable) libraries a.cm and b.cm (that
470    you perhaps didn't write yourself).  Further, suppose each of these
471    two libraries internally uses its own auxiliary library $aux/lib.cm.
472    Normally you would now have a problem because the anchor "lib" can not
473    be bound to more than one value globally.  Therefore, the project that
474    uses both a.cm and b.cm must locally redirect the anchor to some other
475    place:
477       a.cm (bind:(anchor:lib value:/usr/lib/smlnj/a-stuff))
478       b.cm (bind:(anchor:lib value:/usr/lib/smlnj/b-stuff))
480    This hard-wires $lib/aux.cm to /usr/lib/smlnj/a-stuff/aux.cm or
481    /usr/lib/smlnj/b-stuff/aux.cm, respectively.
483    Hard-wiring path names is a bit inflexible (and CM will verbosely warn
484    you when you do so at the time of CM.stabilize).  Therefore, you can
485    also use an anchored path as the value:
487      a.cm (bind:(anchor:lib value:$a-lib))
488      b.cm (bind:(anchor:lib value:$b-lib))
490    Now you can globally configure (using the usual CM.Anchor.anchor or
491    pathconfig machinery) bindings for "a-lib" and "b-lib".  Since "lib"
492    itself is always locally bound, setting it globally is no longer
493    meaningful or necessary (but it does not hurt either).  In fact, "lib"
494    can still be used as a global anchor for separate purposes.  As a
495    matter of fact, one can locally define "lib" in terms of a global
496    "lib":
498      a.cm (bind:(anchor:lib value:$lib/a))
499      b.cm (bind:(anchor:lib value:$lib/b))
501    ** 3: The encoding of path names has changed.  This affects the way
502    path names are shown in CM's progress report and also the internal
503    protocol encoding used for parallel make.
505    The encoding now uses one or more ':'-separated segments.  Each
506    segments corresponds to a file that has been specified relative to the
507    file given by its preceding segment.  The first segment is either
508    relative to the CWD, absolute, or anchored.  Each segment itself is
509    basically a Unix pathname; all segments but the first are relative.
511    Example:
513       $foo/bar/baz.cm:a/b/c.sml
515    This path denotes the file bar/a/b/c.sml relative to the directory
516    denoted by anchor "foo".  Notice that the encoding also includes
517    baz.cm which is the .cm-file that listed a/b/c.sml.  As usual, such
518    paths are resolved relative to the .cm-files directory, so baz.cm must
519    be ignored to get the "real" pathname.
521    To make this fact more obvious, CM puts the names of such "virtual
522    arcs" into parentheses when they appear in progress reports. (No
523    parentheses will appear in the internal protocol encoding.)  Thus,
524    what you really see is:
526      $foo/bar/(baz.cm):a/b/c.sml
528    I find this notation to be much more informative than before.
530    Another new feature of the encoding is that special characters
531    including parentheses, colons, (back)slashes, and white space are
532    written as \ddd (where ddd is the decimal encoding of the character).
534    *** The CM manual still needs to be updated.
536    ----------------------------------------------------------------------
537    Name: Allen Leung
538    Date: 2000/06/15 00:38:00
539    Tag: leunga-20000615-x86-peephole
541    x86 Peephole fix by Fermin.  Affects c-- and moby only.
543    ----------------------------------------------------------------------
544    Name: Matthias Blume
545    Date: 2000/06/12 11:40:00
546    Tag: blume-20000612-parmakefix
547    Description:
549    More cleanup after changing the file naming scheme: This time I
550    repaired the parallel make mechanism for CMB.make which I broke earlier.
552    ----------------------------------------------------------------------
553    Name: Allen Leung
554    Date: 2000/06/09 01:25:00
555    Tag: leunga-20000609-various
557    None of these things should affect normal SML/NJ operations
559    1. Peephole improvements provided by Fermin (c--)
560    2. New annotation DEFUSE for adding extra dependence (moby)
561    3. New X86 LOCK instructions (moby)
562    4. New machine description language for reservation tables (scheduling)
563    5. Fixes to various optimization/analysis modules (branch chaining, dominator
564       trees etc.)
565    6. I've changed the CM files so that they can work with versions
566       110.0.6, 110.25 and 110.28
568    ----------------------------------------------------------------------
569    Name: Matthias Blume
570    Date: 2000/06/09 12:40:00
571    Tag: blume-20000609-log
572    Description:
574    - Removed all(?) remaining RCS Log entries from sources.
576    - Fixed bug in ml-yacc and ml-lex sources (use explicit anchors for
577      anchored paths).
579    ----------------------------------------------------------------------
580    Name: Matthias Blume
581    Date: 2000/06/07 17:00:00 JST
582    Tag: blume-20000607-no-implicit-anchors
583    Description:
585    1. This update changes the default setting for
586    CM.Control.implicit_anchors from true to false.  This means that
587    implicit anchors are no longer permitted by default.  I also tried to
588    make sure that nothing else still relies on implicit anchors.
589    (This is the next step on the schedule towards a CM that does not even
590    have the notion of implicit anchors anymore.)
592    2. More CM manual updates.
594    3. I managed to track down and fix the pickling bug I mentioned last
595    time.  Because of the previously existing workaround, this entails no
596    immediate practical changes.
598    ----------------------------------------------------------------------
599  Name: Matthias Blume  Name: Matthias Blume
600  Date: 2000/06/06 11:15:00 JST  Date: 2000/06/06 11:15:00 JST
601  Tag: blume-20000606-lazierpickle  Tag: blume-20000606-lazierpickle
# Line 544  Line 1128 
1129  3.  Assembly  3.  Assembly
1131      When generating assemby, resolve the value of client defined constants,      When generating assembly, resolve the value of client defined constants,
1132      instead of generating symbolic values.  This is controlled by the      instead of generating symbolic values.  This is controlled by the
1133      new flag "asm-resolve-constants", which is default to true.      new flag "asm-resolve-constants", which is default to true.
# Line 567  Line 1151 
1152  To this end, I arranged that instead of "structure Core" as "structure  To this end, I arranged that instead of "structure Core" as "structure
1153  _Core" is bound in the pervasive environment.  Core access is done via  _Core" is bound in the pervasive environment.  Core access is done via
1154  _Core (which can never be accidentially rebound because _Core is not a  _Core (which can never be accidentally rebound because _Core is not a
1155  legal surface-syntax symbol).  legal surface-syntax symbol).
1157  The current solution is much cleaner because the core environment is  The current solution is much cleaner because the core environment is
# Line 577  Line 1161 
1161  with dynamic and symbolic parts of the core environment.  with dynamic and symbolic parts of the core environment.
1163  Remaining hackery (to bind the "magic" symbol _Core) is localized in the  Remaining hackery (to bind the "magic" symbol _Core) is localized in the
1164  compilation mananger's bootstrap compiler (actually: in the "init group"  compilation manager's bootstrap compiler (actually: in the "init group"
1165  handling).  See the comments in src/system/smlnj/init/init.cmi for  handling).  See the comments in src/system/smlnj/init/init.cmi for
1166  more details.  more details.
# Line 692  Line 1276 
1276     (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
1277     used).     used).
1279     This was done to accomodate the new "make" and "shell" tools which     This was done to accommodate the new "make" and "shell" tools which
1280     facilitate fairly seemless hookup to portions of code managed using     facilitate fairly seamless hookup to portions of code managed using
1281     Makefiles or Shell scripts.     Makefiles or Shell scripts.
1283     There are no classes "shared" or "private" anymore.  Instead, the     There are no classes "shared" or "private" anymore.  Instead, the
# Line 705  Line 1289 
1290     All existing tools are described in the CM manual.     All existing tools are described in the CM manual.
1292     - Slightly better error handling.  (CM now surpresses many followup     - Slightly better error handling.  (CM now suppresses many followup
1293     error messages that tended to be more annoying than helpful.)     error messages that tended to be more annoying than helpful.)
1295  2. Major changes to the compiler's static environment data structures.  2. Major changes to the compiler's static environment data structures.
# Line 839  Line 1423 
1424       I've changed andl to testl in the floating point test sequence       I've changed andl to testl in the floating point test sequence
1425       whenever appropriate.  The Intel optimization guide states that       whenever appropriate.  The Intel optimization guide states that
1426       testl is perferable to andl.       testl is preferable to andl.
1428  7. RA (x86 only)  7. RA (x86 only)
# Line 1021  Line 1605 
1606  1. Tools.registerStdShellCmdTool (from smlnj/cm/tool.cm) takes an  1. Tools.registerStdShellCmdTool (from smlnj/cm/tool.cm) takes an
1607  additional argument called "template" which is an optional string that  additional argument called "template" which is an optional string that
1608  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
1609  explanation.  explanation.
1611  2. A special-purpose tool can be "regisitered" by simply dropping the  2. A special-purpose tool can be "registered" by simply dropping the
1612  corresponding <...>-tool.cm (and/or <...>-ext.cm) into the same  corresponding <...>-tool.cm (and/or <...>-ext.cm) into the same
1613  directory where the .cm file lives that uses this tool.  (The  directory where the .cm file lives that uses this tool.  (The
1614  behavior/misfeature until now was to look for the tool description  behavior/misfeature until now was to look for the tool description
# Line 1068  Line 1652 
1652  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
1653  <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,
1654  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
1655  perhaps got accidentially killed).  In this case, fixpt will quickly  perhaps got accidentally killed).  In this case, fixpt will quickly
1656  move through what exists before continuing where it left off earlier,  move through what exists before continuing where it left off earlier,
1657  and, thus, saves a lot of time.  and, thus, saves a lot of time.
# Line 1118  Line 1702 
1702    it from that remote directory.    it from that remote directory.
1703    This should simplify installation further:  For machines that have    This should simplify installation further:  For machines that have
1704    access to the internet, just fetch <version>-config.tgz, unpack it,    access to the internet, just fetch <version>-config.tgz, unpack it,
1705    edit config/targets, and go (run config/install.sh).  The scipt will    edit config/targets, and go (run config/install.sh).  The script will
1706    fetch everything else that it might need all by itself.    fetch everything else that it might need all by itself.
1708    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.652  
changed lines
  Added in v.683

ViewVC Help
Powered by ViewVC 1.0.0