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

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