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

SCM Repository

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

Diff of /sml/trunk/HISTORY

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

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

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