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

Legend:
Removed from v.659  
changed lines
  Added in v.705

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