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 645, Mon May 15 07:17:30 2000 UTC revision 675, Fri Jun 23 09:18:18 2000 UTC
# Line 13  Line 13 
13  Description:  Description:
14  ----------------------------------------------------------------------  ----------------------------------------------------------------------
15  Name: Matthias Blume  Name: Matthias Blume
16    Date: 2000/06/23 18:20:00 JST
17    Tag: blume-20000623-btrace
18    Description:
19    
20    This updates adds a backtrace facility to aid programmers in debugging
21    their programs.  This involves the following changes:
22    
23    1. Module system/smlnj/init/core.sml (structure _Core) now has hooks for
24       keeping track of the current call stack.  When programs are compiled
25       in a special mode, the compiler will insert calls to these hooks
26       into the user program.
27       "Hook" means that it is possible for different implementations of
28       back-tracing to register themselves (at different times).
29    
30    2. compiler/MiscUtil/profile/btrace.sml implements the annotation phase
31       as an Absyn.dec->Absyn.dec rewrite.  Normally this phase is turned off.
32       It can be turned on using this call:
33         SMLofNJ.Internals.BTrace.mode (SOME true);
34       Turning it off again:
35         SMLofNJ.Internals.BTrace.mode (SOME false);
36       Querying the current status:
37         SMLofNJ.Internals.BTrace.mode NONE;
38       Annotated programs are about twice as big as normal ones, and they
39       run a factor of 2 to 4 slower with a dummy back-trace plugin (one
40       where all hooks do nothing).  The slowdown with a plugin that is
41       actually useful (such as the one supplied by default) is even greater,
42       but in the case of the default plugin it is still only an constant
43       factor (amortized).
44    
45    3. system/Basis/Implementation/NJ/internals.{sig,sml} have been augmented
46       with a sub-structure BTrace for controlling back-tracing.  In particular,
47       the above-mentioned function "mode" controls whether the annotation
48       phase is invoked by the compiler.  Another important function is
49       "trigger": when called it aborts the current execution and causes
50       the top-level loop to print a full back-trace.
51    
52    4. compiler/MiscUtil/profile/btimp.sml is the current default plugin
53       for back-tracing.  It keeps track of the dynamic call stack and in
54       addition to that it keeps a partial history at each "level" of that
55       stack.  For example, if a tail-calls b, b tail-calls c, and c tail-calls
56       d and b (at separate times, dynamically), then the report will show:
57    
58       GOTO   d
59             /c
60       GOTO  \b
61       CALL   a
62    
63       This shows that there was an initial non-tail call of a, then a
64       tail-call to b or c, looping behavior in a cluster of functions that
65       consist of b and c, and then a goto from that cluster (i.e., either from
66       b or from c) to d.
67    
68       Note that (depending on the user program) the amount of information
69       that the back-trace module has to keep track of at each level is bounded
70       by a constant.  Thus, the whole implementation has the same asymptotical
71       complexity as the original program (both in space and in time).
72    
73    5. compiler/TopLevel/interact/evalloop.sml has been modified to
74       handle the special exception SMLofNJ.Internals.BTrace.BTrace
75       which is raised by the "trigger" function mentioned above.
76    
77    Notes on usage:
78    
79    - Annotated code works well together with unannotated code:
80    Unannotated calls simply do not show up at all in the backtrace.
81    
82    - It is not a good idea to let modules that were annotated during
83    different sessions run at the same time.  This is because the compiler
84    chooses small integers to identify individual functions, and there
85    will be clashes if different modules were compiled in separate sessions.
86    (Nothing will crash, and you will even be told about the clashes, but
87    back-trace information will in general not be useful.)
88    
89    - Back-tracing can be confused by callcc and capture.
90    
91    - The only way of getting a back-trace right now is to explicitly
92    invoke the "trigger" function from your user program.  Eventually, we
93    should make every exception carry back-trace information (if
94    available).  But since this creates more overhead at "raise"-time
95    (similar to the current exnHistory overhead), I have not yet
96    implemented this.  (The implementation will be rather easy.)  With
97    exceptions carrying back-trace information, this facility will be even
98    more useful because users don't need to modify their programs...
99    
100    - While it is possible to compile the compiler with back-trace
101    annotations turned on (I did it to get some confidence in
102    correctness), you must make absolutely sure that core.sml and
103    btimp.sml are compiled WITHOUT annotation!  (core.sml cannot actually
104    be compiled with annotation because there is no core access yet, but
105    if you compile btimp.sml with annotation, then the system will go into
106    an infinite recursion and crash.)
107    Since CM currently does not know about BTrace, the only way to turn
108    annotations on and off for different modules of the compiler is to
109    interrupt CMB.make, change the settings, and re-invoke it.  Of course,
110    this is awkward and clumsy.
111    
112    Sample sessions:
113    
114    Standard ML of New Jersey v110.28.1 [FLINT v1.5], June 5, 2000
115    - SMLofNJ.Internals.BTrace.mode (SOME true);
116    [autoloading]
117    [autoloading done]
118    val it = false : bool
119    - structure X = struct
120    -     fun main n = let
121    -         fun a (x, 0) = d x
122    -           | a (x, n) = b (x, n - 1)
123    -         and b (x, n) = c (x, n)
124    -         and c (x, n) = a (x, n)
125    -         and d x = e (x, 3)
126    -         and e (x, 0) = f x
127    -           | e (x, n) = e (x, n - 1)
128    -         and f 0 = SMLofNJ.Internals.BTrace.trigger ()
129    -           | f n = n * g (n - 1)
130    -         and g n = a (n, 3)
131    -     in
132    -         f n
133    -     end
134    - end;
135    structure X : sig val main : int -> int end
136    - X.main 3;
137    *** BACK-TRACE ***
138    GOTO   stdIn:4.2-13.20: X.main[2].f
139    GOTO-( stdIn:4.2-13.20: X.main[2].e
140    GOTO   stdIn:4.2-13.20: X.main[2].d
141         / stdIn:4.2-13.20: X.main[2].a
142         | stdIn:4.2-13.20: X.main[2].b
143    GOTO-\ stdIn:4.2-13.20: X.main[2].c
144    CALL   stdIn:4.2-13.20: X.main[2].g
145    GOTO   stdIn:4.2-13.20: X.main[2].f
146    GOTO-( stdIn:4.2-13.20: X.main[2].e
147    GOTO   stdIn:4.2-13.20: X.main[2].d
148         / stdIn:4.2-13.20: X.main[2].a
149         | stdIn:4.2-13.20: X.main[2].b
150    GOTO-\ stdIn:4.2-13.20: X.main[2].c
151    CALL   stdIn:4.2-13.20: X.main[2].g
152    GOTO   stdIn:4.2-13.20: X.main[2].f
153    GOTO-( stdIn:4.2-13.20: X.main[2].e
154    GOTO   stdIn:4.2-13.20: X.main[2].d
155         / stdIn:4.2-13.20: X.main[2].a
156         | stdIn:4.2-13.20: X.main[2].b
157    GOTO-\ stdIn:4.2-13.20: X.main[2].c
158    CALL   stdIn:4.2-13.20: X.main[2].g
159    GOTO   stdIn:4.2-13.20: X.main[2].f
160    CALL   stdIn:2.15-17.4: X.main[2]
161    -
162    
163    (Note that because of a FLINt bug the above code currently does not
164    compile without BTrace turned on.)
165    
166    Here is another example, using my modified Tiger compiler:
167    
168    Standard ML of New Jersey v110.28.1 [FLINT v1.5], June 5, 2000
169    - SMLofNJ.Internals.BTrace.mode (SOME true);
170    [autoloading]
171    [autoloading done]
172    val it = false : bool
173    - CM.make "sources.cm";
174    [autoloading]
175    ...
176    [autoloading done]
177    [scanning sources.cm]
178    [parsing (sources.cm):parse.sml]
179    [creating directory CM/SKEL ...]
180    [parsing (sources.cm):tiger.lex.sml]
181    ...
182    [wrote CM/sparc-unix/semant.sml]
183    [compiling (sources.cm):main.sml]
184    [wrote CM/sparc-unix/main.sml]
185    [New bindings added.]
186    val it = true : bool
187    - Main.compile ("../testcases/merge.tig", "foo.out");
188    *** BACK-TRACE ***
189    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trvar
190    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
191    CALL   lib/semant.sml:289.3-295.22: SemantFun[2].transExp.trexp.check[2]
192    GOTO   lib/semant.sml:289.3-295.22: SemantFun[2].transExp.trexp.check[2]
193    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
194    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
195    CALL   lib/semant.sml:488.3-505.6: SemantFun[2].transDec.trdec[2].transBody[2]
196         / lib/semant.sml:411.65-543.8: SemantFun[2].transDec
197    CALL-\ lib/semant.sml:413.2-540.9: SemantFun[2].transDec.trdec[2]
198    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
199    CALL   lib/semant.sml:8.52-558.4: SemantFun[2].transProg[2]
200    CALL   main.sml:1.18-118.4: Main.compile[2]
201    -
202    
203    ----------------------------------------------------------------------
204    Name: Matthias Blumen
205    Date: 2000/06/21 18:00:00 JST
206    Tag: blume-20000621-manual
207    Description:
208    
209    CM manual update: Path environments documented.
210    
211    ----------------------------------------------------------------------
212    Name: Matthias Blume
213    Date: 2000/06/19 13:40:00
214    Tag: blume-20000619-manual
215    Description:
216    
217    CM manual and system/README update.  This only covers the fact that
218    there are no more implicit anchors.  (Path environments and the "bind"
219    option to "cm" have yet to be documented.)
220    
221    ----------------------------------------------------------------------
222    Name: Matthias Blume
223    Date: 2000/06/19 11:05:00 JST
224    Tag: blume-20000619-chdir-bugfix
225    Description:
226    
227    Fixed a bug in new SrcPath module that sometimes led to a bad chDir call.
228    
229    ----------------------------------------------------------------------
230    Name: Matthias Blume
231    Date: 2000/06/18 22:00:10 JST
232    Tag: blume-20000618-implicit-anchors-really-gone
233    Description:
234    
235    I updates the previous HISTORY entry where I forgot to mention that
236    implicit anchors are no longer with us.
237    
238    The current update also gets rid of the (now useless) controller
239    CM.Control.implicit_anchors.
240    
241    ----------------------------------------------------------------------
242    Name: Matthias Blume
243    Date: 2000/06/16 17:30:00 JST
244    Tag: blume-20000616-anchorenv
245    Description:
246    
247    This patch implements the long anticipated (just kidding :) "anchor
248    environment" mechanism.  In the course of doing this, I also
249    re-implemented CM's internal "SrcPath" module from scratch.  The new
250    one should be more robust in certain boundary cases.  In any case, it
251    is a lot cleaner than its predecessor (IMHO).
252    
253    This time, although there is yet another boot file format change, I
254    kept the unpickler backward-compatible.  As a result, no new bootfiles
255    are necessary and bootstrapping is straightforward.  (You cannot read
256    new bootfiles into an old system, but the other way around is no
257    problem.)
258    
259    Visible changes:
260    
261    ** 0. Implicit path anchors (without the leading $-symbol) are no
262    longer recognized at all. This means that such path names are not
263    illegal either.  For example, the name basis.cm simply refers to a
264    local file called "basis.cm" (i.e, the name is an ordinary path
265    relative to .cm-files directory).  Or, to put it differently, only
266    names that start with $ are anchored paths.
267    
268    ** 1. The $<singlearc> abbreviation for $/<singlearc> has finally
269    vanished.
270    
271    John (Reppy) had critizised this as soon as I originally proposed and
272    implemented it, but at that time I did not really deeply believe
273    him. :) Now I came full-circle because I need the $<singlearc> syntax
274    in another place where it cannot be seen as an abbreviation for
275    $/<singlearc>.  To avoid the confusion, $<singlearc> now means what it
276    seems to mean (i.e., it "expands" into the corresponding anchor
277    value).
278    
279    However, when paths are used as members in CM description files, it
280    continues to be true that there must be at least another arc after the
281    anchor.  This is now enforced separately during semantic analysis
282    (i.e., from a lexical/syntactical point of view, the notation is ok.)
283    
284    ** 2. The "cm" class now accepts an option "bind".  The option's value
285    is a sub-option list of precisely two items -- one labeled "anchor"
286    and the other one labeled "value".  As you might expect, "anchor" is
287    used to specify an anchor name to be bound, and "value" specifies what
288    the anchor is being bound to.
289    
290    The value must be a directory name and can be given in either standard
291    syntax (including the possibility that it is itself an anchored path)
292    or native syntax.
293    
294    Examples:
295    
296       foo.cm (bind:(anchor:bar value:$mystuff/bar))
297       lib.cm (bind:(anchor:a value:"H:\\x\\y\\z"))  (* only works under windows *)
298    
299    and so on.
300    
301    The meaning of this is that the .cm-file will be processed with an
302    augmented anchor environment where the given anchor(s) is/are bound to
303    the given values(s).
304    
305    The rationale for having this feature is this: Suppose you are trying
306    to use two different (already stable) libraries a.cm and b.cm (that
307    you perhaps didn't write yourself).  Further, suppose each of these
308    two libraries internally uses its own auxiliary library $aux/lib.cm.
309    Normally you would now have a problem because the anchor "lib" can not
310    be bound to more than one value globally.  Therefore, the project that
311    uses both a.cm and b.cm must locally redirect the anchor to some other
312    place:
313    
314       a.cm (bind:(anchor:lib value:/usr/lib/smlnj/a-stuff))
315       b.cm (bind:(anchor:lib value:/usr/lib/smlnj/b-stuff))
316    
317    This hard-wires $lib/aux.cm to /usr/lib/smlnj/a-stuff/aux.cm or
318    /usr/lib/smlnj/b-stuff/aux.cm, respectively.
319    
320    Hard-wiring path names is a bit inflexible (and CM will verbosely warn
321    you when you do so at the time of CM.stabilize).  Therefore, you can
322    also use an anchored path as the value:
323    
324      a.cm (bind:(anchor:lib value:$a-lib))
325      b.cm (bind:(anchor:lib value:$b-lib))
326    
327    Now you can globally configure (using the usual CM.Anchor.anchor or
328    pathconfig machinery) bindings for "a-lib" and "b-lib".  Since "lib"
329    itself is always locally bound, setting it globally is no longer
330    meaningful or necessary (but it does not hurt either).  In fact, "lib"
331    can still be used as a global anchor for separate purposes.  As a
332    matter of fact, one can locally define "lib" in terms of a global
333    "lib":
334    
335      a.cm (bind:(anchor:lib value:$lib/a))
336      b.cm (bind:(anchor:lib value:$lib/b))
337    
338    ** 3: The encoding of path names has changed.  This affects the way
339    path names are shown in CM's progress report and also the internal
340    protocol encoding used for parallel make.
341    
342    The encoding now uses one or more ':'-separated segments.  Each
343    segments corresponds to a file that has been specified relative to the
344    file given by its preceding segment.  The first segment is either
345    relative to the CWD, absolute, or anchored.  Each segment itself is
346    basically a Unix pathname; all segments but the first are relative.
347    
348    Example:
349    
350       $foo/bar/baz.cm:a/b/c.sml
351    
352    This path denotes the file bar/a/b/c.sml relative to the directory
353    denoted by anchor "foo".  Notice that the encoding also includes
354    baz.cm which is the .cm-file that listed a/b/c.sml.  As usual, such
355    paths are resolved relative to the .cm-files directory, so baz.cm must
356    be ignored to get the "real" pathname.
357    
358    To make this fact more obvious, CM puts the names of such "virtual
359    arcs" into parentheses when they appear in progress reports. (No
360    parentheses will appear in the internal protocol encoding.)  Thus,
361    what you really see is:
362    
363      $foo/bar/(baz.cm):a/b/c.sml
364    
365    I find this notation to be much more informative than before.
366    
367    Another new feature of the encoding is that special characters
368    including parentheses, colons, (back)slashes, and white space are
369    written as \ddd (where ddd is the decimal encoding of the character).
370    
371    *** The CM manual still needs to be updated.
372    
373    ----------------------------------------------------------------------
374    Name: Allen Leung
375    Date: 2000/06/15 00:38:00
376    Tag: leunga-20000615-x86-peephole
377    
378    x86 Peephole fix by Fermin.  Affects c-- and moby only.
379    
380    ----------------------------------------------------------------------
381    Name: Matthias Blume
382    Date: 2000/06/12 11:40:00
383    Tag: blume-20000612-parmakefix
384    Description:
385    
386    More cleanup after changing the file naming scheme: This time I
387    repaired the parallel make mechanism for CMB.make which I broke earlier.
388    
389    ----------------------------------------------------------------------
390    Name: Allen Leung
391    Date: 2000/06/09 01:25:00
392    Tag: leunga-20000609-various
393    
394    None of these things should affect normal SML/NJ operations
395    
396    1. Peephole improvements provided by Fermin (c--)
397    2. New annotation DEFUSE for adding extra dependence (moby)
398    3. New X86 LOCK instructions (moby)
399    4. New machine description language for reservation tables (scheduling)
400    5. Fixes to various optimization/analysis modules (branch chaining, dominator
401       trees etc.)
402    6. I've changed the CM files so that they can work with versions
403       110.0.6, 110.25 and 110.28
404    
405    ----------------------------------------------------------------------
406    Name: Matthias Blume
407    Date: 2000/06/09 12:40:00
408    Tag: blume-20000609-log
409    Description:
410    
411    - Removed all(?) remaining RCS Log entries from sources.
412    
413    - Fixed bug in ml-yacc and ml-lex sources (use explicit anchors for
414      anchored paths).
415    
416    ----------------------------------------------------------------------
417    Name: Matthias Blume
418    Date: 2000/06/07 17:00:00 JST
419    Tag: blume-20000607-no-implicit-anchors
420    Description:
421    
422    1. This update changes the default setting for
423    CM.Control.implicit_anchors from true to false.  This means that
424    implicit anchors are no longer permitted by default.  I also tried to
425    make sure that nothing else still relies on implicit anchors.
426    (This is the next step on the schedule towards a CM that does not even
427    have the notion of implicit anchors anymore.)
428    
429    2. More CM manual updates.
430    
431    3. I managed to track down and fix the pickling bug I mentioned last
432    time.  Because of the previously existing workaround, this entails no
433    immediate practical changes.
434    
435    ----------------------------------------------------------------------
436    Name: Matthias Blume
437    Date: 2000/06/06 11:15:00 JST
438    Tag: blume-20000606-lazierpickle
439    Description:
440    
441    !!!! NEW BOOT FILES !!!!
442    
443    * The main purpose of this update is to make library pickles lazier in
444    order to reduce the initial space penalty for autoloading a library.
445    As a result, it is now possible to have $smlnj/compiler.cm
446    pre-registered.  This should take care of the many complaints or
447    inquiries about missing structure Compiler.  This required changes to
448    CM's internal data structures and small tweaks to some algorithms.
449    
450    As a neat additional effect, it is no longer necessary (for the sake
451    of lean heap image files) to distinguish between a "minimal" CM and a
452    "full" CM.  Now, there is only one CM (i.e., the "full" version:
453    $smlnj/cm.cm aka $smlnj/cm/full.cm), and it is always available at the
454    interactive top level. ($smlnj/cm/minimal.cm is gone.)
455    
456    To make the life of compiler-hackers easier, "makeml" now also
457    pre-registers $smlnj/cmb.cm (aka $smlnj/cmb/current.cm).  In other
458    words, after you bootstrap a new sml for the first time, you will not
459    have to autoload $smlnj/cmb.cm again afterwards.  (The first time
460    around you will still have to do it, though.)
461    
462    * A second change consists of major updates to the CM manual.  There
463    are now several appendices with summary information and also a full
464    specification of the CM description file syntax.
465    
466    * In directory src/system I added the script "allcross".  This script
467    invokes sml and cross-compiles the compiler for all supported
468    architectures.  (Useful when providing a new set of boot files.)
469    
470    * There seems to be a latent bug in my "lazy pickles" mechanism.  I
471    added a small tweak to pickle-util.sml to work around this problem,
472    but it is not a proper fix yet.  I will investigate further.  (The
473    effect of the bug was an inflation of library pickle size.)
474    
475    * Version number increased to 110.28.1 (to avoid compatibility problems).
476    
477    ----------------------------------------------------------------------
478    Name: Allen Leung
479    Date: 2000/05/25 17:28 EDT
480    Tag: leunga-20000525-ra
481    Description:
482    
483      Fixed a bug in freezing phase of the register allocator.
484    
485    ----------------------------------------------------------------------
486    Name: Allen Leung
487    Date: 2000/05/15 22:53 EDT
488    Tag: leunga-20000515-alpha-x86-ra
489    Description:
490    
491      1. Alpha
492    
493          Slight cleanup.  Removed the instruction SGNXL
494    
495      2. X86
496    
497          Added the following instructions to the instruction set:
498    
499            ROLx, RORx,
500            BTx, BTSx, BTLx, BTRx,
501            XCHGx, and variants with the LOCK prefix
502    
503      3. Register Allocation
504    
505          The module ra-rewrite-with-renaming has been improved.
506    
507      These have no effect on SML/NJ.
508    
509    ----------------------------------------------------------------------
510    Name: Matthias Blume
511  Date: 2000/05/15 16:20:00 JST  Date: 2000/05/15 16:20:00 JST
512  Tag: blume-20000515-lightrebuild  Tag: blume-20000515-lightrebuild
513  Description:  Description:
# Line 470  Line 965 
965    
966  3.  Assembly  3.  Assembly
967    
968      When generating assemby, resolve the value of client defined constants,      When generating assembly, resolve the value of client defined constants,
969      instead of generating symbolic values.  This is controlled by the      instead of generating symbolic values.  This is controlled by the
970      new flag "asm-resolve-constants", which is default to true.      new flag "asm-resolve-constants", which is default to true.
971    
# Line 493  Line 988 
988    
989  To this end, I arranged that instead of "structure Core" as "structure  To this end, I arranged that instead of "structure Core" as "structure
990  _Core" is bound in the pervasive environment.  Core access is done via  _Core" is bound in the pervasive environment.  Core access is done via
991  _Core (which can never be accidentially rebound because _Core is not a  _Core (which can never be accidentally rebound because _Core is not a
992  legal surface-syntax symbol).  legal surface-syntax symbol).
993    
994  The current solution is much cleaner because the core environment is  The current solution is much cleaner because the core environment is
# Line 503  Line 998 
998  with dynamic and symbolic parts of the core environment.  with dynamic and symbolic parts of the core environment.
999    
1000  Remaining hackery (to bind the "magic" symbol _Core) is localized in the  Remaining hackery (to bind the "magic" symbol _Core) is localized in the
1001  compilation mananger's bootstrap compiler (actually: in the "init group"  compilation manager's bootstrap compiler (actually: in the "init group"
1002  handling).  See the comments in src/system/smlnj/init/init.cmi for  handling).  See the comments in src/system/smlnj/init/init.cmi for
1003  more details.  more details.
1004    
# Line 618  Line 1113 
1113     (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
1114     used).     used).
1115    
1116     This was done to accomodate the new "make" and "shell" tools which     This was done to accommodate the new "make" and "shell" tools which
1117     facilitate fairly seemless hookup to portions of code managed using     facilitate fairly seamless hookup to portions of code managed using
1118     Makefiles or Shell scripts.     Makefiles or Shell scripts.
1119    
1120     There are no classes "shared" or "private" anymore.  Instead, the     There are no classes "shared" or "private" anymore.  Instead, the
# Line 631  Line 1126 
1126    
1127     All existing tools are described in the CM manual.     All existing tools are described in the CM manual.
1128    
1129     - Slightly better error handling.  (CM now surpresses many followup     - Slightly better error handling.  (CM now suppresses many followup
1130     error messages that tended to be more annoying than helpful.)     error messages that tended to be more annoying than helpful.)
1131    
1132  2. Major changes to the compiler's static environment data structures.  2. Major changes to the compiler's static environment data structures.
# Line 765  Line 1260 
1260    
1261       I've changed andl to testl in the floating point test sequence       I've changed andl to testl in the floating point test sequence
1262       whenever appropriate.  The Intel optimization guide states that       whenever appropriate.  The Intel optimization guide states that
1263       testl is perferable to andl.       testl is preferable to andl.
1264    
1265  7. RA (x86 only)  7. RA (x86 only)
1266    
# Line 947  Line 1442 
1442    
1443  1. Tools.registerStdShellCmdTool (from smlnj/cm/tool.cm) takes an  1. Tools.registerStdShellCmdTool (from smlnj/cm/tool.cm) takes an
1444  additional argument called "template" which is an optional string that  additional argument called "template" which is an optional string that
1445  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
1446  explanation.  explanation.
1447    
1448  2. A special-purpose tool can be "regisitered" by simply dropping the  2. A special-purpose tool can be "registered" by simply dropping the
1449  corresponding <...>-tool.cm (and/or <...>-ext.cm) into the same  corresponding <...>-tool.cm (and/or <...>-ext.cm) into the same
1450  directory where the .cm file lives that uses this tool.  (The  directory where the .cm file lives that uses this tool.  (The
1451  behavior/misfeature until now was to look for the tool description  behavior/misfeature until now was to look for the tool description
# Line 994  Line 1489 
1489  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
1490  <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,
1491  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
1492  perhaps got accidentially killed).  In this case, fixpt will quickly  perhaps got accidentally killed).  In this case, fixpt will quickly
1493  move through what exists before continuing where it left off earlier,  move through what exists before continuing where it left off earlier,
1494  and, thus, saves a lot of time.  and, thus, saves a lot of time.
1495    
# Line 1044  Line 1539 
1539    it from that remote directory.    it from that remote directory.
1540    This should simplify installation further:  For machines that have    This should simplify installation further:  For machines that have
1541    access to the internet, just fetch <version>-config.tgz, unpack it,    access to the internet, just fetch <version>-config.tgz, unpack it,
1542    edit config/targets, and go (run config/install.sh).  The scipt will    edit config/targets, and go (run config/install.sh).  The script will
1543    fetch everything else that it might need all by itself.    fetch everything else that it might need all by itself.
1544    
1545    For CVS users, this mechanism is not relevant for source archives, but    For CVS users, this mechanism is not relevant for source archives, but

Legend:
Removed from v.645  
changed lines
  Added in v.675

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