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 697, Tue Aug 8 03:33:13 2000 UTC
# Line 13  Line 13 
13  Description:  Description:
14  ----------------------------------------------------------------------  ----------------------------------------------------------------------
15  Name: Matthias Blume  Name: Matthias Blume
16    Date: 2000/08/08 12:33:00 JST
17    Tag: blume-20000808-manual
18    Description:
19    
20    Tiny update to CM manual.
21    
22    ----------------------------------------------------------------------
23    Name: Allen Leung
24    Date: 2000/08/7 19:31:00
25    Tag: leunga-20000807-a-whole-bunch-of-stuff
26    
27      Moby, C--, SSA, x86, machine descriptions etc.  Should only affect C--
28    and Mobdy.
29    
30    1.  x86
31    
32       a.  Fixes to peephole module by John and Dan.
33       b.  Assembly fix to SETcc by Allen.
34       c.  Fix to c-call by John.
35       d.  Fix to spilling by John.  (This one deals with the missing FSTPT case)
36       e.  Instruction selection optimization to SETcc as suggested by John.
37    
38           For example,
39    
40            MV(32, x, COND(32, CMP(32, LT, a, b), LI 1, LI 0))
41    
42           should generate:
43    
44            MOVL a, x
45            SUBL b, x
46            SHRL 31, x
47    
48    2.  IR stuff
49    
50         A bunch of new DJ-graph related algorithms added.  These
51         speed up SSA construction.
52    
53    3.  SSA + Scheduling
54    
55         Added code for SSA and scheduling to the repository
56    
57    ----------------------------------------------------------------------
58    Name: Lal George
59    Date: 2000/07/27 11:53:14 EDT
60    
61    Tag: lal-20000727-linux-ppc
62    Description:
63    
64     Made changes to support Linux PPC.
65     p.s. I have confirmation that the 110.29 boot files work fine.
66    
67    ----------------------------------------------------------------------
68    Name: Matthias Blume
69    Date: 2000/07/27 17:40:00 JST
70    Tag: blume-20000727-scripts
71    Description:
72    
73    !!!! WARNING !!!!
74    You must recompile the runtime system!
75    !!!! WARNING !!!!
76    
77    This is basically another round of script-enhancements:
78    
79    1. sml, ml-build, and ml-makedepend accept options -D and -U to define
80       and undefine CM preprocessor symbols.
81    
82    2. ml-build avoids generating a new heap image if it finds that the
83       existing one is still ok.  (The condition is that no ML file had to
84       be recompiled and all ML files are found to be older that the heap
85       file.)
86    
87       To make this work smoothly, I also hacked the runtime system as
88       well as SMLofNJ.SysInfo to get access to the heap image suffix
89       (.sparc-solaris, ...) that is currently being used.
90    
91       Moreover, the signature of CM.mk_standalone has changed.  See the
92       CM manual.
93    
94    3. ml-makedepend accepts additional options -n, -a, and -o.  (See the
95       CM manual for details.)
96    
97    4. More CM manual updates:
98        - all of the above has been documented.
99        - there is now a section describing the (CM-related) command line
100          arguments that are accepted by the "sml" command
101    
102    ----------------------------------------------------------------------
103    Name: Matthias Blume
104    Date: 2000/07/25 16:20:00 JST
105    Tag: blume-20000725-makedepend
106    Description:
107    
108    Added a script called ml-makedepend.  This can be used in makefiles
109    for Unix' make in a way very similar to the "makedepend" command for
110    C.
111    
112    The script internally uses function CM.sources.
113    
114    Synopsis:
115    
116        ml-makedepend [-f makefile] cmfile targetname
117    
118    The default for the makefile is "makefile" (or "Makefile" should
119    "makefile" not exist).
120    
121    ml-makedepend adds a cmfile/targetname-specific section to this
122    makefile (after removing the previous version of this section).  The
123    section contains a single dependency specification with targetname on
124    the LHS (targetname is an arbitrary name), and a list of files derived
125    from the cmfile on the RHS.  Some of the files on the RHS are
126    ARCH/OPSYS-specific.  Therefore, ml-makedepend inserts references to
127    "make" variables $(ARCH) and $(OPSYS) in place of the corresponding
128    path names.  The makefile writer is responsible for making sure that
129    these variables have correct at the time "make" is invoked.
130    
131    ----------------------------------------------------------------------
132    Name: Matthias Blume
133    Date: 2000/07/22 23:30:00 JST
134    Tag: blume-20000722-urlupdate
135    Description:
136    
137    Changed BOOT and config/srcarchiveurl to point to BL server:
138    
139        ftp://ftp.research.bell-labs.com/dist/smlnj/working/110.29/
140    
141    ----------------------------------------------------------------------
142    Name: Matthias Blume
143    Date: 2000/07/18 18:00:00 JST
144    Tag: blume-20000718-Version_110_29
145    Description:
146    
147    1. Updated src/compiler/TopLevel/main/version.sml to version 110.29
148    
149    2. Updated config/version to 110.29
150    
151    3. Updated config/srcarchiveurl
152    
153    3. New boot files!
154       ftp://ftp.cs.princeton.edu/pub/people/blume/sml/110.29-autofetch
155    
156    ----------------------------------------------------------------------
157    Name: Matthias Blume
158    Date: 2000/07/11 13:58:00 JST
159    Tag: blume-20000711-doctypo
160    Description:
161    
162    Fixed a few typos in CM manual.
163    
164    ----------------------------------------------------------------------
165    Name: Allen Leung
166    Date: 2000/06/15 00:38:00
167    Tag: leunga-20000704-sparc-x86
168    
169    1. x86 peephole improvement sp += k; sp -= k => nop  [from John]
170    2. fix to x86 RET bug [found by Dan Grossman]
171    3. sparc assembly bug fix for ticc instructions [found by Fermin]
172    
173       Affects c-- and moby only
174    
175    ----------------------------------------------------------------------
176    Name: Matthias Blume
177    Date: 2000/07/04 15:26:00
178    Tag: blume-20000704-trigger
179    Description:
180    
181    1. Improvements to CM manual.
182    2. SMLofNJ.Internals.BTrace.trigger reinstated as an alternative way
183       of getting a back-trace.  The function, when called, raises an
184       internal exception which explicitly carries the full back-trace history,
185       so it is unaffected by any intervening handle-raise pairs ("trivial"
186       or not).  The interactive loop will print that history once it arrives
187       at top level.
188       Short of having all exceptions implicitly carry the full history, the
189       recommended way of using this facility is:
190         - compile your program with instrumentation "on"
191         - run it, when it raises an exception, look at the history
192         - if the history is "cut off" because of some handler, go and modify
193           your program so that it explicitly calls BTrace.trigger
194         - recompile (still instrumented), and rerun; look at the full history
195    
196    ----------------------------------------------------------------------
197    Name: Matthias Blume
198    Date: 2000/07/03 15:36:00 JST
199    Tag: blume-20000702-manual
200    Description:
201    
202    Small corrections and updates to CM manual.
203    
204    ----------------------------------------------------------------------
205    Name: Matthias Blume
206    Date: 2000/06/29 16:04:00 JST
207    Tag: blume-20000629-yacctool
208    Description:
209    
210    Changes:
211    
212    1. Class "mlyacc" now takes separate arguments to pass options to
213       generated .sml- and .sig-files independently.
214    2. Corresponding CM manual updates.
215    3. BTrace module now also reports call sites.  (However, for loop clusters
216       it only shows from where the cluster was entered.)  There are associated
217       modifications to core.sml, internals.{sig,sml}, btrace.sml, and btimp.sml.
218    
219    ----------------------------------------------------------------------
220    Name: Matthias Blume
221    Date: 2000/06/27 16:51:00 JST
222    Tag: blume-20000627-noweb
223    Description:
224    
225    Changes:
226    
227     1. Implemented "subdir" and "witness" options for noweb tool.
228        This caused some slight internal changes in CM's tool implementation.
229     2. Fixed bug in "tool plugin" mechanism.  This is essentially cleaning
230        some remaining issues from earlier path anchor changes.
231     3. Updated CM manual accordingly.
232    
233     4. Changed implementation of back-tracing so that I now consider it
234        ready for prime-time.
235    
236        In particular, you don't have to explicitly trigger the back-trace
237        anymore.  Instead, if you are running BTrace-instrumented code and
238        there is an uncaught exception (regardless of whether or not it was
239        raised in instrumented code), the top-level evalloop will print
240        the back-trace.
241    
242        Features:
243    
244          - Instrumented and uninstrumented code work together seemlessly.
245            (Of course, uninstrumented code is never mentioned in actual
246             back-traces.)
247    
248          - Asymptotic time- and space-complexity of instrumented code is
249            equal to that of uninstrumented code.  (This means that
250            tail-recursion is preserved by the instrumentation phase.)
251    
252          - Modules whose code has been instrumented in different sessions
253            work together without problem.
254    
255          - There is no penalty whatsoever on uninstrumented code.
256    
257          - There is no penalty on "raise" expressions, even in
258            instrumented code.
259    
260        A potential bug (or perhaps it is a feature, too):
261    
262          A back-trace reaches no further than the outermost instrumented
263          non-trivial "raise".  Here, a "trivial" raise is one that is the
264          sole RHS of a "handle" rule.  Thus, back-traces reach trough
265    
266               <exp> handle e => raise e
267    
268          and even
269    
270               <exp> handle Foo => raise Bar
271    
272          and, of course, through
273    
274               <exp> handle Foo => ...
275    
276         if the exception was not Foo.
277    
278         Back-traces always reach right through any un-instrumented code
279         including any of its "handle" expressions, trivial or not.
280    
281       To try this out, do the following:
282    
283         - Erase all existing binfiles for your program.
284           (You may keep binfiles for those modules where you think you
285            definitely don't need back-tracing.)
286         - Turn on back-trace instrumentation:
287              SMLofNJ.Internals.BTrace.mode (SOME true);
288         - Recompile your program.  (I.e., run "CM.make" or "use".)
289         - You may now turn instrumentation off again (if you want):
290              SMLofNJ.Internals.BTrace.mode (SOME false);
291         - Run your program as usual.  If it raises an exception that
292           reaches the interactive toplevel, then a back-trace will
293           automatically be printed.  After that, the toplevel loop
294           will print the exception history as usual.
295    
296    ----------------------------------------------------------------------
297    Name: Matthias Blume
298    Date: 2000/06/26 09:56:46 JST
299    Tag: blume-20000626-setup
300    Description:
301    
302    CM: - setup-parameter to "sml" added; this can be used to run arbitrary
303          ML code before and after compiling a file (e.g., to set compiler
304          flags)
305    
306    Compiler: - improved btrace API (in core.sml, internals.{sig,sml})
307              - associated changes to btrace.sml (BTrace instrumentation pass)
308              - cleaner implementation of btimp.sml (BTrace tracing and report
309                module)
310    
311    CM manual: * new path encoding documented
312               * description of setup-parameter to "sml" added
313    
314    The biggest user-visible change to back-tracing is that it is no
315    longer necessary to compile all traced modules within the same
316    session.  (This was a real limitation.)
317    
318    ----------------------------------------------------------------------
319    Name: Matthias Blume
320    Date: 2000/06/24 12:40:00 JST
321    Tag: blume-20000624-startup
322    Description:
323    
324    Fixes startup slowdown problem.  (I was calling SrcPath.sync a _tad_
325    bit too often -- to put it mildly. :)
326    
327    ----------------------------------------------------------------------
328    Name: Matthias Blume
329    Date: 2000/06/23 18:20:00 JST
330    Tag: blume-20000623-btrace
331    Description:
332    
333    This updates adds a backtrace facility to aid programmers in debugging
334    their programs.  This involves the following changes:
335    
336    1. Module system/smlnj/init/core.sml (structure _Core) now has hooks for
337       keeping track of the current call stack.  When programs are compiled
338       in a special mode, the compiler will insert calls to these hooks
339       into the user program.
340       "Hook" means that it is possible for different implementations of
341       back-tracing to register themselves (at different times).
342    
343    2. compiler/MiscUtil/profile/btrace.sml implements the annotation phase
344       as an Absyn.dec->Absyn.dec rewrite.  Normally this phase is turned off.
345       It can be turned on using this call:
346         SMLofNJ.Internals.BTrace.mode (SOME true);
347       Turning it off again:
348         SMLofNJ.Internals.BTrace.mode (SOME false);
349       Querying the current status:
350         SMLofNJ.Internals.BTrace.mode NONE;
351       Annotated programs are about twice as big as normal ones, and they
352       run a factor of 2 to 4 slower with a dummy back-trace plugin (one
353       where all hooks do nothing).  The slowdown with a plugin that is
354       actually useful (such as the one supplied by default) is even greater,
355       but in the case of the default plugin it is still only an constant
356       factor (amortized).
357    
358    3. system/Basis/Implementation/NJ/internals.{sig,sml} have been augmented
359       with a sub-structure BTrace for controlling back-tracing.  In particular,
360       the above-mentioned function "mode" controls whether the annotation
361       phase is invoked by the compiler.  Another important function is
362       "trigger": when called it aborts the current execution and causes
363       the top-level loop to print a full back-trace.
364    
365    4. compiler/MiscUtil/profile/btimp.sml is the current default plugin
366       for back-tracing.  It keeps track of the dynamic call stack and in
367       addition to that it keeps a partial history at each "level" of that
368       stack.  For example, if a tail-calls b, b tail-calls c, and c tail-calls
369       d and b (at separate times, dynamically), then the report will show:
370    
371       GOTO   d
372             /c
373       GOTO  \b
374       CALL   a
375    
376       This shows that there was an initial non-tail call of a, then a
377       tail-call to b or c, looping behavior in a cluster of functions that
378       consist of b and c, and then a goto from that cluster (i.e., either from
379       b or from c) to d.
380    
381       Note that (depending on the user program) the amount of information
382       that the back-trace module has to keep track of at each level is bounded
383       by a constant.  Thus, the whole implementation has the same asymptotical
384       complexity as the original program (both in space and in time).
385    
386    5. compiler/TopLevel/interact/evalloop.sml has been modified to
387       handle the special exception SMLofNJ.Internals.BTrace.BTrace
388       which is raised by the "trigger" function mentioned above.
389    
390    Notes on usage:
391    
392    - Annotated code works well together with unannotated code:
393    Unannotated calls simply do not show up at all in the backtrace.
394    
395    - It is not a good idea to let modules that were annotated during
396    different sessions run at the same time.  This is because the compiler
397    chooses small integers to identify individual functions, and there
398    will be clashes if different modules were compiled in separate sessions.
399    (Nothing will crash, and you will even be told about the clashes, but
400    back-trace information will in general not be useful.)
401    
402    - Back-tracing can be confused by callcc and capture.
403    
404    - The only way of getting a back-trace right now is to explicitly
405    invoke the "trigger" function from your user program.  Eventually, we
406    should make every exception carry back-trace information (if
407    available).  But since this creates more overhead at "raise"-time
408    (similar to the current exnHistory overhead), I have not yet
409    implemented this.  (The implementation will be rather easy.)  With
410    exceptions carrying back-trace information, this facility will be even
411    more useful because users don't need to modify their programs...
412    
413    - While it is possible to compile the compiler with back-trace
414    annotations turned on (I did it to get some confidence in
415    correctness), you must make absolutely sure that core.sml and
416    btimp.sml are compiled WITHOUT annotation!  (core.sml cannot actually
417    be compiled with annotation because there is no core access yet, but
418    if you compile btimp.sml with annotation, then the system will go into
419    an infinite recursion and crash.)
420    Since CM currently does not know about BTrace, the only way to turn
421    annotations on and off for different modules of the compiler is to
422    interrupt CMB.make, change the settings, and re-invoke it.  Of course,
423    this is awkward and clumsy.
424    
425    Sample sessions:
426    
427    Standard ML of New Jersey v110.28.1 [FLINT v1.5], June 5, 2000
428    - SMLofNJ.Internals.BTrace.mode (SOME true);
429    [autoloading]
430    [autoloading done]
431    val it = false : bool
432    - structure X = struct
433    -     fun main n = let
434    -         fun a (x, 0) = d x
435    -           | a (x, n) = b (x, n - 1)
436    -         and b (x, n) = c (x, n)
437    -         and c (x, n) = a (x, n)
438    -         and d x = e (x, 3)
439    -         and e (x, 0) = f x
440    -           | e (x, n) = e (x, n - 1)
441    -         and f 0 = SMLofNJ.Internals.BTrace.trigger ()
442    -           | f n = n * g (n - 1)
443    -         and g n = a (n, 3)
444    -     in
445    -         f n
446    -     end
447    - end;
448    structure X : sig val main : int -> int end
449    - X.main 3;
450    *** BACK-TRACE ***
451    GOTO   stdIn:4.2-13.20: X.main[2].f
452    GOTO-( stdIn:4.2-13.20: X.main[2].e
453    GOTO   stdIn:4.2-13.20: X.main[2].d
454         / stdIn:4.2-13.20: X.main[2].a
455         | stdIn:4.2-13.20: X.main[2].b
456    GOTO-\ stdIn:4.2-13.20: X.main[2].c
457    CALL   stdIn:4.2-13.20: X.main[2].g
458    GOTO   stdIn:4.2-13.20: X.main[2].f
459    GOTO-( stdIn:4.2-13.20: X.main[2].e
460    GOTO   stdIn:4.2-13.20: X.main[2].d
461         / stdIn:4.2-13.20: X.main[2].a
462         | stdIn:4.2-13.20: X.main[2].b
463    GOTO-\ stdIn:4.2-13.20: X.main[2].c
464    CALL   stdIn:4.2-13.20: X.main[2].g
465    GOTO   stdIn:4.2-13.20: X.main[2].f
466    GOTO-( stdIn:4.2-13.20: X.main[2].e
467    GOTO   stdIn:4.2-13.20: X.main[2].d
468         / stdIn:4.2-13.20: X.main[2].a
469         | stdIn:4.2-13.20: X.main[2].b
470    GOTO-\ stdIn:4.2-13.20: X.main[2].c
471    CALL   stdIn:4.2-13.20: X.main[2].g
472    GOTO   stdIn:4.2-13.20: X.main[2].f
473    CALL   stdIn:2.15-17.4: X.main[2]
474    -
475    
476    (Note that because of a FLINt bug the above code currently does not
477    compile without BTrace turned on.)
478    
479    Here is another example, using my modified Tiger compiler:
480    
481    Standard ML of New Jersey v110.28.1 [FLINT v1.5], June 5, 2000
482    - SMLofNJ.Internals.BTrace.mode (SOME true);
483    [autoloading]
484    [autoloading done]
485    val it = false : bool
486    - CM.make "sources.cm";
487    [autoloading]
488    ...
489    [autoloading done]
490    [scanning sources.cm]
491    [parsing (sources.cm):parse.sml]
492    [creating directory CM/SKEL ...]
493    [parsing (sources.cm):tiger.lex.sml]
494    ...
495    [wrote CM/sparc-unix/semant.sml]
496    [compiling (sources.cm):main.sml]
497    [wrote CM/sparc-unix/main.sml]
498    [New bindings added.]
499    val it = true : bool
500    - Main.compile ("../testcases/merge.tig", "foo.out");
501    *** BACK-TRACE ***
502    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trvar
503    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
504    CALL   lib/semant.sml:289.3-295.22: SemantFun[2].transExp.trexp.check[2]
505    GOTO   lib/semant.sml:289.3-295.22: SemantFun[2].transExp.trexp.check[2]
506    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
507    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
508    CALL   lib/semant.sml:488.3-505.6: SemantFun[2].transDec.trdec[2].transBody[2]
509         / lib/semant.sml:411.65-543.8: SemantFun[2].transDec
510    CALL-\ lib/semant.sml:413.2-540.9: SemantFun[2].transDec.trdec[2]
511    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
512    CALL   lib/semant.sml:8.52-558.4: SemantFun[2].transProg[2]
513    CALL   main.sml:1.18-118.4: Main.compile[2]
514    -
515    
516    ----------------------------------------------------------------------
517    Name: Matthias Blumen
518    Date: 2000/06/21 18:00:00 JST
519    Tag: blume-20000621-manual
520    Description:
521    
522    CM manual update: Path environments documented.
523    
524    ----------------------------------------------------------------------
525    Name: Matthias Blume
526    Date: 2000/06/19 13:40:00
527    Tag: blume-20000619-manual
528    Description:
529    
530    CM manual and system/README update.  This only covers the fact that
531    there are no more implicit anchors.  (Path environments and the "bind"
532    option to "cm" have yet to be documented.)
533    
534    ----------------------------------------------------------------------
535    Name: Matthias Blume
536    Date: 2000/06/19 11:05:00 JST
537    Tag: blume-20000619-chdir-bugfix
538    Description:
539    
540    Fixed a bug in new SrcPath module that sometimes led to a bad chDir call.
541    
542    ----------------------------------------------------------------------
543    Name: Matthias Blume
544    Date: 2000/06/18 22:00:10 JST
545    Tag: blume-20000618-implicit-anchors-really-gone
546    Description:
547    
548    I updates the previous HISTORY entry where I forgot to mention that
549    implicit anchors are no longer with us.
550    
551    The current update also gets rid of the (now useless) controller
552    CM.Control.implicit_anchors.
553    
554    ----------------------------------------------------------------------
555    Name: Matthias Blume
556    Date: 2000/06/16 17:30:00 JST
557    Tag: blume-20000616-anchorenv
558    Description:
559    
560    This patch implements the long anticipated (just kidding :) "anchor
561    environment" mechanism.  In the course of doing this, I also
562    re-implemented CM's internal "SrcPath" module from scratch.  The new
563    one should be more robust in certain boundary cases.  In any case, it
564    is a lot cleaner than its predecessor (IMHO).
565    
566    This time, although there is yet another boot file format change, I
567    kept the unpickler backward-compatible.  As a result, no new bootfiles
568    are necessary and bootstrapping is straightforward.  (You cannot read
569    new bootfiles into an old system, but the other way around is no
570    problem.)
571    
572    Visible changes:
573    
574    ** 0. Implicit path anchors (without the leading $-symbol) are no
575    longer recognized at all. This means that such path names are not
576    illegal either.  For example, the name basis.cm simply refers to a
577    local file called "basis.cm" (i.e, the name is an ordinary path
578    relative to .cm-files directory).  Or, to put it differently, only
579    names that start with $ are anchored paths.
580    
581    ** 1. The $<singlearc> abbreviation for $/<singlearc> has finally
582    vanished.
583    
584    John (Reppy) had critizised this as soon as I originally proposed and
585    implemented it, but at that time I did not really deeply believe
586    him. :) Now I came full-circle because I need the $<singlearc> syntax
587    in another place where it cannot be seen as an abbreviation for
588    $/<singlearc>.  To avoid the confusion, $<singlearc> now means what it
589    seems to mean (i.e., it "expands" into the corresponding anchor
590    value).
591    
592    However, when paths are used as members in CM description files, it
593    continues to be true that there must be at least another arc after the
594    anchor.  This is now enforced separately during semantic analysis
595    (i.e., from a lexical/syntactical point of view, the notation is ok.)
596    
597    ** 2. The "cm" class now accepts an option "bind".  The option's value
598    is a sub-option list of precisely two items -- one labeled "anchor"
599    and the other one labeled "value".  As you might expect, "anchor" is
600    used to specify an anchor name to be bound, and "value" specifies what
601    the anchor is being bound to.
602    
603    The value must be a directory name and can be given in either standard
604    syntax (including the possibility that it is itself an anchored path)
605    or native syntax.
606    
607    Examples:
608    
609       foo.cm (bind:(anchor:bar value:$mystuff/bar))
610       lib.cm (bind:(anchor:a value:"H:\\x\\y\\z"))  (* only works under windows *)
611    
612    and so on.
613    
614    The meaning of this is that the .cm-file will be processed with an
615    augmented anchor environment where the given anchor(s) is/are bound to
616    the given values(s).
617    
618    The rationale for having this feature is this: Suppose you are trying
619    to use two different (already stable) libraries a.cm and b.cm (that
620    you perhaps didn't write yourself).  Further, suppose each of these
621    two libraries internally uses its own auxiliary library $aux/lib.cm.
622    Normally you would now have a problem because the anchor "lib" can not
623    be bound to more than one value globally.  Therefore, the project that
624    uses both a.cm and b.cm must locally redirect the anchor to some other
625    place:
626    
627       a.cm (bind:(anchor:lib value:/usr/lib/smlnj/a-stuff))
628       b.cm (bind:(anchor:lib value:/usr/lib/smlnj/b-stuff))
629    
630    This hard-wires $lib/aux.cm to /usr/lib/smlnj/a-stuff/aux.cm or
631    /usr/lib/smlnj/b-stuff/aux.cm, respectively.
632    
633    Hard-wiring path names is a bit inflexible (and CM will verbosely warn
634    you when you do so at the time of CM.stabilize).  Therefore, you can
635    also use an anchored path as the value:
636    
637      a.cm (bind:(anchor:lib value:$a-lib))
638      b.cm (bind:(anchor:lib value:$b-lib))
639    
640    Now you can globally configure (using the usual CM.Anchor.anchor or
641    pathconfig machinery) bindings for "a-lib" and "b-lib".  Since "lib"
642    itself is always locally bound, setting it globally is no longer
643    meaningful or necessary (but it does not hurt either).  In fact, "lib"
644    can still be used as a global anchor for separate purposes.  As a
645    matter of fact, one can locally define "lib" in terms of a global
646    "lib":
647    
648      a.cm (bind:(anchor:lib value:$lib/a))
649      b.cm (bind:(anchor:lib value:$lib/b))
650    
651    ** 3: The encoding of path names has changed.  This affects the way
652    path names are shown in CM's progress report and also the internal
653    protocol encoding used for parallel make.
654    
655    The encoding now uses one or more ':'-separated segments.  Each
656    segments corresponds to a file that has been specified relative to the
657    file given by its preceding segment.  The first segment is either
658    relative to the CWD, absolute, or anchored.  Each segment itself is
659    basically a Unix pathname; all segments but the first are relative.
660    
661    Example:
662    
663       $foo/bar/baz.cm:a/b/c.sml
664    
665    This path denotes the file bar/a/b/c.sml relative to the directory
666    denoted by anchor "foo".  Notice that the encoding also includes
667    baz.cm which is the .cm-file that listed a/b/c.sml.  As usual, such
668    paths are resolved relative to the .cm-files directory, so baz.cm must
669    be ignored to get the "real" pathname.
670    
671    To make this fact more obvious, CM puts the names of such "virtual
672    arcs" into parentheses when they appear in progress reports. (No
673    parentheses will appear in the internal protocol encoding.)  Thus,
674    what you really see is:
675    
676      $foo/bar/(baz.cm):a/b/c.sml
677    
678    I find this notation to be much more informative than before.
679    
680    Another new feature of the encoding is that special characters
681    including parentheses, colons, (back)slashes, and white space are
682    written as \ddd (where ddd is the decimal encoding of the character).
683    
684    *** The CM manual still needs to be updated.
685    
686    ----------------------------------------------------------------------
687    Name: Allen Leung
688    Date: 2000/06/15 00:38:00
689    Tag: leunga-20000615-x86-peephole
690    
691    x86 Peephole fix by Fermin.  Affects c-- and moby only.
692    
693    ----------------------------------------------------------------------
694    Name: Matthias Blume
695    Date: 2000/06/12 11:40:00
696    Tag: blume-20000612-parmakefix
697    Description:
698    
699    More cleanup after changing the file naming scheme: This time I
700    repaired the parallel make mechanism for CMB.make which I broke earlier.
701    
702    ----------------------------------------------------------------------
703    Name: Allen Leung
704    Date: 2000/06/09 01:25:00
705    Tag: leunga-20000609-various
706    
707    None of these things should affect normal SML/NJ operations
708    
709    1. Peephole improvements provided by Fermin (c--)
710    2. New annotation DEFUSE for adding extra dependence (moby)
711    3. New X86 LOCK instructions (moby)
712    4. New machine description language for reservation tables (scheduling)
713    5. Fixes to various optimization/analysis modules (branch chaining, dominator
714       trees etc.)
715    6. I've changed the CM files so that they can work with versions
716       110.0.6, 110.25 and 110.28
717    
718    ----------------------------------------------------------------------
719    Name: Matthias Blume
720    Date: 2000/06/09 12:40:00
721    Tag: blume-20000609-log
722    Description:
723    
724    - Removed all(?) remaining RCS Log entries from sources.
725    
726    - Fixed bug in ml-yacc and ml-lex sources (use explicit anchors for
727      anchored paths).
728    
729    ----------------------------------------------------------------------
730    Name: Matthias Blume
731    Date: 2000/06/07 17:00:00 JST
732    Tag: blume-20000607-no-implicit-anchors
733    Description:
734    
735    1. This update changes the default setting for
736    CM.Control.implicit_anchors from true to false.  This means that
737    implicit anchors are no longer permitted by default.  I also tried to
738    make sure that nothing else still relies on implicit anchors.
739    (This is the next step on the schedule towards a CM that does not even
740    have the notion of implicit anchors anymore.)
741    
742    2. More CM manual updates.
743    
744    3. I managed to track down and fix the pickling bug I mentioned last
745    time.  Because of the previously existing workaround, this entails no
746    immediate practical changes.
747    
748    ----------------------------------------------------------------------
749    Name: Matthias Blume
750    Date: 2000/06/06 11:15:00 JST
751    Tag: blume-20000606-lazierpickle
752    Description:
753    
754    !!!! NEW BOOT FILES !!!!
755    
756    * The main purpose of this update is to make library pickles lazier in
757    order to reduce the initial space penalty for autoloading a library.
758    As a result, it is now possible to have $smlnj/compiler.cm
759    pre-registered.  This should take care of the many complaints or
760    inquiries about missing structure Compiler.  This required changes to
761    CM's internal data structures and small tweaks to some algorithms.
762    
763    As a neat additional effect, it is no longer necessary (for the sake
764    of lean heap image files) to distinguish between a "minimal" CM and a
765    "full" CM.  Now, there is only one CM (i.e., the "full" version:
766    $smlnj/cm.cm aka $smlnj/cm/full.cm), and it is always available at the
767    interactive top level. ($smlnj/cm/minimal.cm is gone.)
768    
769    To make the life of compiler-hackers easier, "makeml" now also
770    pre-registers $smlnj/cmb.cm (aka $smlnj/cmb/current.cm).  In other
771    words, after you bootstrap a new sml for the first time, you will not
772    have to autoload $smlnj/cmb.cm again afterwards.  (The first time
773    around you will still have to do it, though.)
774    
775    * A second change consists of major updates to the CM manual.  There
776    are now several appendices with summary information and also a full
777    specification of the CM description file syntax.
778    
779    * In directory src/system I added the script "allcross".  This script
780    invokes sml and cross-compiles the compiler for all supported
781    architectures.  (Useful when providing a new set of boot files.)
782    
783    * There seems to be a latent bug in my "lazy pickles" mechanism.  I
784    added a small tweak to pickle-util.sml to work around this problem,
785    but it is not a proper fix yet.  I will investigate further.  (The
786    effect of the bug was an inflation of library pickle size.)
787    
788    * Version number increased to 110.28.1 (to avoid compatibility problems).
789    
790    ----------------------------------------------------------------------
791    Name: Allen Leung
792    Date: 2000/05/25 17:28 EDT
793    Tag: leunga-20000525-ra
794    Description:
795    
796      Fixed a bug in freezing phase of the register allocator.
797    
798    ----------------------------------------------------------------------
799    Name: Allen Leung
800    Date: 2000/05/15 22:53 EDT
801    Tag: leunga-20000515-alpha-x86-ra
802    Description:
803    
804      1. Alpha
805    
806          Slight cleanup.  Removed the instruction SGNXL
807    
808      2. X86
809    
810          Added the following instructions to the instruction set:
811    
812            ROLx, RORx,
813            BTx, BTSx, BTLx, BTRx,
814            XCHGx, and variants with the LOCK prefix
815    
816      3. Register Allocation
817    
818          The module ra-rewrite-with-renaming has been improved.
819    
820      These have no effect on SML/NJ.
821    
822    ----------------------------------------------------------------------
823    Name: Matthias Blume
824  Date: 2000/05/15 16:20:00 JST  Date: 2000/05/15 16:20:00 JST
825  Tag: blume-20000515-lightrebuild  Tag: blume-20000515-lightrebuild
826  Description:  Description:
# Line 470  Line 1278 
1278    
1279  3.  Assembly  3.  Assembly
1280    
1281      When generating assemby, resolve the value of client defined constants,      When generating assembly, resolve the value of client defined constants,
1282      instead of generating symbolic values.  This is controlled by the      instead of generating symbolic values.  This is controlled by the
1283      new flag "asm-resolve-constants", which is default to true.      new flag "asm-resolve-constants", which is default to true.
1284    
# Line 493  Line 1301 
1301    
1302  To this end, I arranged that instead of "structure Core" as "structure  To this end, I arranged that instead of "structure Core" as "structure
1303  _Core" is bound in the pervasive environment.  Core access is done via  _Core" is bound in the pervasive environment.  Core access is done via
1304  _Core (which can never be accidentially rebound because _Core is not a  _Core (which can never be accidentally rebound because _Core is not a
1305  legal surface-syntax symbol).  legal surface-syntax symbol).
1306    
1307  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 1311 
1311  with dynamic and symbolic parts of the core environment.  with dynamic and symbolic parts of the core environment.
1312    
1313  Remaining hackery (to bind the "magic" symbol _Core) is localized in the  Remaining hackery (to bind the "magic" symbol _Core) is localized in the
1314  compilation mananger's bootstrap compiler (actually: in the "init group"  compilation manager's bootstrap compiler (actually: in the "init group"
1315  handling).  See the comments in src/system/smlnj/init/init.cmi for  handling).  See the comments in src/system/smlnj/init/init.cmi for
1316  more details.  more details.
1317    
# Line 618  Line 1426 
1426     (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
1427     used).     used).
1428    
1429     This was done to accomodate the new "make" and "shell" tools which     This was done to accommodate the new "make" and "shell" tools which
1430     facilitate fairly seemless hookup to portions of code managed using     facilitate fairly seamless hookup to portions of code managed using
1431     Makefiles or Shell scripts.     Makefiles or Shell scripts.
1432    
1433     There are no classes "shared" or "private" anymore.  Instead, the     There are no classes "shared" or "private" anymore.  Instead, the
# Line 631  Line 1439 
1439    
1440     All existing tools are described in the CM manual.     All existing tools are described in the CM manual.
1441    
1442     - Slightly better error handling.  (CM now surpresses many followup     - Slightly better error handling.  (CM now suppresses many followup
1443     error messages that tended to be more annoying than helpful.)     error messages that tended to be more annoying than helpful.)
1444    
1445  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 1573 
1573    
1574       I've changed andl to testl in the floating point test sequence       I've changed andl to testl in the floating point test sequence
1575       whenever appropriate.  The Intel optimization guide states that       whenever appropriate.  The Intel optimization guide states that
1576       testl is perferable to andl.       testl is preferable to andl.
1577    
1578  7. RA (x86 only)  7. RA (x86 only)
1579    
# Line 947  Line 1755 
1755    
1756  1. Tools.registerStdShellCmdTool (from smlnj/cm/tool.cm) takes an  1. Tools.registerStdShellCmdTool (from smlnj/cm/tool.cm) takes an
1757  additional argument called "template" which is an optional string that  additional argument called "template" which is an optional string that
1758  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
1759  explanation.  explanation.
1760    
1761  2. A special-purpose tool can be "regisitered" by simply dropping the  2. A special-purpose tool can be "registered" by simply dropping the
1762  corresponding <...>-tool.cm (and/or <...>-ext.cm) into the same  corresponding <...>-tool.cm (and/or <...>-ext.cm) into the same
1763  directory where the .cm file lives that uses this tool.  (The  directory where the .cm file lives that uses this tool.  (The
1764  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 1802 
1802  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
1803  <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,
1804  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
1805  perhaps got accidentially killed).  In this case, fixpt will quickly  perhaps got accidentally killed).  In this case, fixpt will quickly
1806  move through what exists before continuing where it left off earlier,  move through what exists before continuing where it left off earlier,
1807  and, thus, saves a lot of time.  and, thus, saves a lot of time.
1808    
# Line 1044  Line 1852 
1852    it from that remote directory.    it from that remote directory.
1853    This should simplify installation further:  For machines that have    This should simplify installation further:  For machines that have
1854    access to the internet, just fetch <version>-config.tgz, unpack it,    access to the internet, just fetch <version>-config.tgz, unpack it,
1855    edit config/targets, and go (run config/install.sh).  The scipt will    edit config/targets, and go (run config/install.sh).  The script will
1856    fetch everything else that it might need all by itself.    fetch everything else that it might need all by itself.
1857    
1858    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.697

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