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

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