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 656, Fri Jun 9 03:39:04 2000 UTC revision 676, Sat Jun 24 03:37:03 2000 UTC
# Line 13  Line 13 
13  Description:  Description:
14  ----------------------------------------------------------------------  ----------------------------------------------------------------------
15  Name: Matthias Blume  Name: Matthias Blume
16    Date: 2000/06/24 12:40:00 JST
17    Tag: blume-20000624-startup
18    Description:
19    
20    Fixes startup slowdown problem.  (I was calling SrcPath.sync a _tad_
21    bit too often -- to put it mildly. :)
22    
23    ----------------------------------------------------------------------
24    Name: Matthias Blume
25    Date: 2000/06/23 18:20:00 JST
26    Tag: blume-20000623-btrace
27    Description:
28    
29    This updates adds a backtrace facility to aid programmers in debugging
30    their programs.  This involves the following changes:
31    
32    1. Module system/smlnj/init/core.sml (structure _Core) now has hooks for
33       keeping track of the current call stack.  When programs are compiled
34       in a special mode, the compiler will insert calls to these hooks
35       into the user program.
36       "Hook" means that it is possible for different implementations of
37       back-tracing to register themselves (at different times).
38    
39    2. compiler/MiscUtil/profile/btrace.sml implements the annotation phase
40       as an Absyn.dec->Absyn.dec rewrite.  Normally this phase is turned off.
41       It can be turned on using this call:
42         SMLofNJ.Internals.BTrace.mode (SOME true);
43       Turning it off again:
44         SMLofNJ.Internals.BTrace.mode (SOME false);
45       Querying the current status:
46         SMLofNJ.Internals.BTrace.mode NONE;
47       Annotated programs are about twice as big as normal ones, and they
48       run a factor of 2 to 4 slower with a dummy back-trace plugin (one
49       where all hooks do nothing).  The slowdown with a plugin that is
50       actually useful (such as the one supplied by default) is even greater,
51       but in the case of the default plugin it is still only an constant
52       factor (amortized).
53    
54    3. system/Basis/Implementation/NJ/internals.{sig,sml} have been augmented
55       with a sub-structure BTrace for controlling back-tracing.  In particular,
56       the above-mentioned function "mode" controls whether the annotation
57       phase is invoked by the compiler.  Another important function is
58       "trigger": when called it aborts the current execution and causes
59       the top-level loop to print a full back-trace.
60    
61    4. compiler/MiscUtil/profile/btimp.sml is the current default plugin
62       for back-tracing.  It keeps track of the dynamic call stack and in
63       addition to that it keeps a partial history at each "level" of that
64       stack.  For example, if a tail-calls b, b tail-calls c, and c tail-calls
65       d and b (at separate times, dynamically), then the report will show:
66    
67       GOTO   d
68             /c
69       GOTO  \b
70       CALL   a
71    
72       This shows that there was an initial non-tail call of a, then a
73       tail-call to b or c, looping behavior in a cluster of functions that
74       consist of b and c, and then a goto from that cluster (i.e., either from
75       b or from c) to d.
76    
77       Note that (depending on the user program) the amount of information
78       that the back-trace module has to keep track of at each level is bounded
79       by a constant.  Thus, the whole implementation has the same asymptotical
80       complexity as the original program (both in space and in time).
81    
82    5. compiler/TopLevel/interact/evalloop.sml has been modified to
83       handle the special exception SMLofNJ.Internals.BTrace.BTrace
84       which is raised by the "trigger" function mentioned above.
85    
86    Notes on usage:
87    
88    - Annotated code works well together with unannotated code:
89    Unannotated calls simply do not show up at all in the backtrace.
90    
91    - It is not a good idea to let modules that were annotated during
92    different sessions run at the same time.  This is because the compiler
93    chooses small integers to identify individual functions, and there
94    will be clashes if different modules were compiled in separate sessions.
95    (Nothing will crash, and you will even be told about the clashes, but
96    back-trace information will in general not be useful.)
97    
98    - Back-tracing can be confused by callcc and capture.
99    
100    - The only way of getting a back-trace right now is to explicitly
101    invoke the "trigger" function from your user program.  Eventually, we
102    should make every exception carry back-trace information (if
103    available).  But since this creates more overhead at "raise"-time
104    (similar to the current exnHistory overhead), I have not yet
105    implemented this.  (The implementation will be rather easy.)  With
106    exceptions carrying back-trace information, this facility will be even
107    more useful because users don't need to modify their programs...
108    
109    - While it is possible to compile the compiler with back-trace
110    annotations turned on (I did it to get some confidence in
111    correctness), you must make absolutely sure that core.sml and
112    btimp.sml are compiled WITHOUT annotation!  (core.sml cannot actually
113    be compiled with annotation because there is no core access yet, but
114    if you compile btimp.sml with annotation, then the system will go into
115    an infinite recursion and crash.)
116    Since CM currently does not know about BTrace, the only way to turn
117    annotations on and off for different modules of the compiler is to
118    interrupt CMB.make, change the settings, and re-invoke it.  Of course,
119    this is awkward and clumsy.
120    
121    Sample sessions:
122    
123    Standard ML of New Jersey v110.28.1 [FLINT v1.5], June 5, 2000
124    - SMLofNJ.Internals.BTrace.mode (SOME true);
125    [autoloading]
126    [autoloading done]
127    val it = false : bool
128    - structure X = struct
129    -     fun main n = let
130    -         fun a (x, 0) = d x
131    -           | a (x, n) = b (x, n - 1)
132    -         and b (x, n) = c (x, n)
133    -         and c (x, n) = a (x, n)
134    -         and d x = e (x, 3)
135    -         and e (x, 0) = f x
136    -           | e (x, n) = e (x, n - 1)
137    -         and f 0 = SMLofNJ.Internals.BTrace.trigger ()
138    -           | f n = n * g (n - 1)
139    -         and g n = a (n, 3)
140    -     in
141    -         f n
142    -     end
143    - end;
144    structure X : sig val main : int -> int end
145    - X.main 3;
146    *** BACK-TRACE ***
147    GOTO   stdIn:4.2-13.20: X.main[2].f
148    GOTO-( stdIn:4.2-13.20: X.main[2].e
149    GOTO   stdIn:4.2-13.20: X.main[2].d
150         / stdIn:4.2-13.20: X.main[2].a
151         | stdIn:4.2-13.20: X.main[2].b
152    GOTO-\ stdIn:4.2-13.20: X.main[2].c
153    CALL   stdIn:4.2-13.20: X.main[2].g
154    GOTO   stdIn:4.2-13.20: X.main[2].f
155    GOTO-( stdIn:4.2-13.20: X.main[2].e
156    GOTO   stdIn:4.2-13.20: X.main[2].d
157         / stdIn:4.2-13.20: X.main[2].a
158         | stdIn:4.2-13.20: X.main[2].b
159    GOTO-\ stdIn:4.2-13.20: X.main[2].c
160    CALL   stdIn:4.2-13.20: X.main[2].g
161    GOTO   stdIn:4.2-13.20: X.main[2].f
162    GOTO-( stdIn:4.2-13.20: X.main[2].e
163    GOTO   stdIn:4.2-13.20: X.main[2].d
164         / stdIn:4.2-13.20: X.main[2].a
165         | stdIn:4.2-13.20: X.main[2].b
166    GOTO-\ stdIn:4.2-13.20: X.main[2].c
167    CALL   stdIn:4.2-13.20: X.main[2].g
168    GOTO   stdIn:4.2-13.20: X.main[2].f
169    CALL   stdIn:2.15-17.4: X.main[2]
170    -
171    
172    (Note that because of a FLINt bug the above code currently does not
173    compile without BTrace turned on.)
174    
175    Here is another example, using my modified Tiger compiler:
176    
177    Standard ML of New Jersey v110.28.1 [FLINT v1.5], June 5, 2000
178    - SMLofNJ.Internals.BTrace.mode (SOME true);
179    [autoloading]
180    [autoloading done]
181    val it = false : bool
182    - CM.make "sources.cm";
183    [autoloading]
184    ...
185    [autoloading done]
186    [scanning sources.cm]
187    [parsing (sources.cm):parse.sml]
188    [creating directory CM/SKEL ...]
189    [parsing (sources.cm):tiger.lex.sml]
190    ...
191    [wrote CM/sparc-unix/semant.sml]
192    [compiling (sources.cm):main.sml]
193    [wrote CM/sparc-unix/main.sml]
194    [New bindings added.]
195    val it = true : bool
196    - Main.compile ("../testcases/merge.tig", "foo.out");
197    *** BACK-TRACE ***
198    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trvar
199    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
200    CALL   lib/semant.sml:289.3-295.22: SemantFun[2].transExp.trexp.check[2]
201    GOTO   lib/semant.sml:289.3-295.22: SemantFun[2].transExp.trexp.check[2]
202    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
203    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
204    CALL   lib/semant.sml:488.3-505.6: SemantFun[2].transDec.trdec[2].transBody[2]
205         / lib/semant.sml:411.65-543.8: SemantFun[2].transDec
206    CALL-\ lib/semant.sml:413.2-540.9: SemantFun[2].transDec.trdec[2]
207    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
208    CALL   lib/semant.sml:8.52-558.4: SemantFun[2].transProg[2]
209    CALL   main.sml:1.18-118.4: Main.compile[2]
210    -
211    
212    ----------------------------------------------------------------------
213    Name: Matthias Blumen
214    Date: 2000/06/21 18:00:00 JST
215    Tag: blume-20000621-manual
216    Description:
217    
218    CM manual update: Path environments documented.
219    
220    ----------------------------------------------------------------------
221    Name: Matthias Blume
222    Date: 2000/06/19 13:40:00
223    Tag: blume-20000619-manual
224    Description:
225    
226    CM manual and system/README update.  This only covers the fact that
227    there are no more implicit anchors.  (Path environments and the "bind"
228    option to "cm" have yet to be documented.)
229    
230    ----------------------------------------------------------------------
231    Name: Matthias Blume
232    Date: 2000/06/19 11:05:00 JST
233    Tag: blume-20000619-chdir-bugfix
234    Description:
235    
236    Fixed a bug in new SrcPath module that sometimes led to a bad chDir call.
237    
238    ----------------------------------------------------------------------
239    Name: Matthias Blume
240    Date: 2000/06/18 22:00:10 JST
241    Tag: blume-20000618-implicit-anchors-really-gone
242    Description:
243    
244    I updates the previous HISTORY entry where I forgot to mention that
245    implicit anchors are no longer with us.
246    
247    The current update also gets rid of the (now useless) controller
248    CM.Control.implicit_anchors.
249    
250    ----------------------------------------------------------------------
251    Name: Matthias Blume
252    Date: 2000/06/16 17:30:00 JST
253    Tag: blume-20000616-anchorenv
254    Description:
255    
256    This patch implements the long anticipated (just kidding :) "anchor
257    environment" mechanism.  In the course of doing this, I also
258    re-implemented CM's internal "SrcPath" module from scratch.  The new
259    one should be more robust in certain boundary cases.  In any case, it
260    is a lot cleaner than its predecessor (IMHO).
261    
262    This time, although there is yet another boot file format change, I
263    kept the unpickler backward-compatible.  As a result, no new bootfiles
264    are necessary and bootstrapping is straightforward.  (You cannot read
265    new bootfiles into an old system, but the other way around is no
266    problem.)
267    
268    Visible changes:
269    
270    ** 0. Implicit path anchors (without the leading $-symbol) are no
271    longer recognized at all. This means that such path names are not
272    illegal either.  For example, the name basis.cm simply refers to a
273    local file called "basis.cm" (i.e, the name is an ordinary path
274    relative to .cm-files directory).  Or, to put it differently, only
275    names that start with $ are anchored paths.
276    
277    ** 1. The $<singlearc> abbreviation for $/<singlearc> has finally
278    vanished.
279    
280    John (Reppy) had critizised this as soon as I originally proposed and
281    implemented it, but at that time I did not really deeply believe
282    him. :) Now I came full-circle because I need the $<singlearc> syntax
283    in another place where it cannot be seen as an abbreviation for
284    $/<singlearc>.  To avoid the confusion, $<singlearc> now means what it
285    seems to mean (i.e., it "expands" into the corresponding anchor
286    value).
287    
288    However, when paths are used as members in CM description files, it
289    continues to be true that there must be at least another arc after the
290    anchor.  This is now enforced separately during semantic analysis
291    (i.e., from a lexical/syntactical point of view, the notation is ok.)
292    
293    ** 2. The "cm" class now accepts an option "bind".  The option's value
294    is a sub-option list of precisely two items -- one labeled "anchor"
295    and the other one labeled "value".  As you might expect, "anchor" is
296    used to specify an anchor name to be bound, and "value" specifies what
297    the anchor is being bound to.
298    
299    The value must be a directory name and can be given in either standard
300    syntax (including the possibility that it is itself an anchored path)
301    or native syntax.
302    
303    Examples:
304    
305       foo.cm (bind:(anchor:bar value:$mystuff/bar))
306       lib.cm (bind:(anchor:a value:"H:\\x\\y\\z"))  (* only works under windows *)
307    
308    and so on.
309    
310    The meaning of this is that the .cm-file will be processed with an
311    augmented anchor environment where the given anchor(s) is/are bound to
312    the given values(s).
313    
314    The rationale for having this feature is this: Suppose you are trying
315    to use two different (already stable) libraries a.cm and b.cm (that
316    you perhaps didn't write yourself).  Further, suppose each of these
317    two libraries internally uses its own auxiliary library $aux/lib.cm.
318    Normally you would now have a problem because the anchor "lib" can not
319    be bound to more than one value globally.  Therefore, the project that
320    uses both a.cm and b.cm must locally redirect the anchor to some other
321    place:
322    
323       a.cm (bind:(anchor:lib value:/usr/lib/smlnj/a-stuff))
324       b.cm (bind:(anchor:lib value:/usr/lib/smlnj/b-stuff))
325    
326    This hard-wires $lib/aux.cm to /usr/lib/smlnj/a-stuff/aux.cm or
327    /usr/lib/smlnj/b-stuff/aux.cm, respectively.
328    
329    Hard-wiring path names is a bit inflexible (and CM will verbosely warn
330    you when you do so at the time of CM.stabilize).  Therefore, you can
331    also use an anchored path as the value:
332    
333      a.cm (bind:(anchor:lib value:$a-lib))
334      b.cm (bind:(anchor:lib value:$b-lib))
335    
336    Now you can globally configure (using the usual CM.Anchor.anchor or
337    pathconfig machinery) bindings for "a-lib" and "b-lib".  Since "lib"
338    itself is always locally bound, setting it globally is no longer
339    meaningful or necessary (but it does not hurt either).  In fact, "lib"
340    can still be used as a global anchor for separate purposes.  As a
341    matter of fact, one can locally define "lib" in terms of a global
342    "lib":
343    
344      a.cm (bind:(anchor:lib value:$lib/a))
345      b.cm (bind:(anchor:lib value:$lib/b))
346    
347    ** 3: The encoding of path names has changed.  This affects the way
348    path names are shown in CM's progress report and also the internal
349    protocol encoding used for parallel make.
350    
351    The encoding now uses one or more ':'-separated segments.  Each
352    segments corresponds to a file that has been specified relative to the
353    file given by its preceding segment.  The first segment is either
354    relative to the CWD, absolute, or anchored.  Each segment itself is
355    basically a Unix pathname; all segments but the first are relative.
356    
357    Example:
358    
359       $foo/bar/baz.cm:a/b/c.sml
360    
361    This path denotes the file bar/a/b/c.sml relative to the directory
362    denoted by anchor "foo".  Notice that the encoding also includes
363    baz.cm which is the .cm-file that listed a/b/c.sml.  As usual, such
364    paths are resolved relative to the .cm-files directory, so baz.cm must
365    be ignored to get the "real" pathname.
366    
367    To make this fact more obvious, CM puts the names of such "virtual
368    arcs" into parentheses when they appear in progress reports. (No
369    parentheses will appear in the internal protocol encoding.)  Thus,
370    what you really see is:
371    
372      $foo/bar/(baz.cm):a/b/c.sml
373    
374    I find this notation to be much more informative than before.
375    
376    Another new feature of the encoding is that special characters
377    including parentheses, colons, (back)slashes, and white space are
378    written as \ddd (where ddd is the decimal encoding of the character).
379    
380    *** The CM manual still needs to be updated.
381    
382    ----------------------------------------------------------------------
383    Name: Allen Leung
384    Date: 2000/06/15 00:38:00
385    Tag: leunga-20000615-x86-peephole
386    
387    x86 Peephole fix by Fermin.  Affects c-- and moby only.
388    
389    ----------------------------------------------------------------------
390    Name: Matthias Blume
391    Date: 2000/06/12 11:40:00
392    Tag: blume-20000612-parmakefix
393    Description:
394    
395    More cleanup after changing the file naming scheme: This time I
396    repaired the parallel make mechanism for CMB.make which I broke earlier.
397    
398    ----------------------------------------------------------------------
399    Name: Allen Leung
400    Date: 2000/06/09 01:25:00
401    Tag: leunga-20000609-various
402    
403    None of these things should affect normal SML/NJ operations
404    
405    1. Peephole improvements provided by Fermin (c--)
406    2. New annotation DEFUSE for adding extra dependence (moby)
407    3. New X86 LOCK instructions (moby)
408    4. New machine description language for reservation tables (scheduling)
409    5. Fixes to various optimization/analysis modules (branch chaining, dominator
410       trees etc.)
411    6. I've changed the CM files so that they can work with versions
412       110.0.6, 110.25 and 110.28
413    
414    ----------------------------------------------------------------------
415    Name: Matthias Blume
416  Date: 2000/06/09 12:40:00  Date: 2000/06/09 12:40:00
417  Tag: blume-20000609-log  Tag: blume-20000609-log
418  Description:  Description:
# Line 574  Line 974 
974    
975  3.  Assembly  3.  Assembly
976    
977      When generating assemby, resolve the value of client defined constants,      When generating assembly, resolve the value of client defined constants,
978      instead of generating symbolic values.  This is controlled by the      instead of generating symbolic values.  This is controlled by the
979      new flag "asm-resolve-constants", which is default to true.      new flag "asm-resolve-constants", which is default to true.
980    
# Line 597  Line 997 
997    
998  To this end, I arranged that instead of "structure Core" as "structure  To this end, I arranged that instead of "structure Core" as "structure
999  _Core" is bound in the pervasive environment.  Core access is done via  _Core" is bound in the pervasive environment.  Core access is done via
1000  _Core (which can never be accidentially rebound because _Core is not a  _Core (which can never be accidentally rebound because _Core is not a
1001  legal surface-syntax symbol).  legal surface-syntax symbol).
1002    
1003  The current solution is much cleaner because the core environment is  The current solution is much cleaner because the core environment is
# Line 607  Line 1007 
1007  with dynamic and symbolic parts of the core environment.  with dynamic and symbolic parts of the core environment.
1008    
1009  Remaining hackery (to bind the "magic" symbol _Core) is localized in the  Remaining hackery (to bind the "magic" symbol _Core) is localized in the
1010  compilation mananger's bootstrap compiler (actually: in the "init group"  compilation manager's bootstrap compiler (actually: in the "init group"
1011  handling).  See the comments in src/system/smlnj/init/init.cmi for  handling).  See the comments in src/system/smlnj/init/init.cmi for
1012  more details.  more details.
1013    
# Line 722  Line 1122 
1122     (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
1123     used).     used).
1124    
1125     This was done to accomodate the new "make" and "shell" tools which     This was done to accommodate the new "make" and "shell" tools which
1126     facilitate fairly seemless hookup to portions of code managed using     facilitate fairly seamless hookup to portions of code managed using
1127     Makefiles or Shell scripts.     Makefiles or Shell scripts.
1128    
1129     There are no classes "shared" or "private" anymore.  Instead, the     There are no classes "shared" or "private" anymore.  Instead, the
# Line 735  Line 1135 
1135    
1136     All existing tools are described in the CM manual.     All existing tools are described in the CM manual.
1137    
1138     - Slightly better error handling.  (CM now surpresses many followup     - Slightly better error handling.  (CM now suppresses many followup
1139     error messages that tended to be more annoying than helpful.)     error messages that tended to be more annoying than helpful.)
1140    
1141  2. Major changes to the compiler's static environment data structures.  2. Major changes to the compiler's static environment data structures.
# Line 869  Line 1269 
1269    
1270       I've changed andl to testl in the floating point test sequence       I've changed andl to testl in the floating point test sequence
1271       whenever appropriate.  The Intel optimization guide states that       whenever appropriate.  The Intel optimization guide states that
1272       testl is perferable to andl.       testl is preferable to andl.
1273    
1274  7. RA (x86 only)  7. RA (x86 only)
1275    
# Line 1051  Line 1451 
1451    
1452  1. Tools.registerStdShellCmdTool (from smlnj/cm/tool.cm) takes an  1. Tools.registerStdShellCmdTool (from smlnj/cm/tool.cm) takes an
1453  additional argument called "template" which is an optional string that  additional argument called "template" which is an optional string that
1454  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
1455  explanation.  explanation.
1456    
1457  2. A special-purpose tool can be "regisitered" by simply dropping the  2. A special-purpose tool can be "registered" by simply dropping the
1458  corresponding <...>-tool.cm (and/or <...>-ext.cm) into the same  corresponding <...>-tool.cm (and/or <...>-ext.cm) into the same
1459  directory where the .cm file lives that uses this tool.  (The  directory where the .cm file lives that uses this tool.  (The
1460  behavior/misfeature until now was to look for the tool description  behavior/misfeature until now was to look for the tool description
# Line 1098  Line 1498 
1498  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
1499  <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,
1500  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
1501  perhaps got accidentially killed).  In this case, fixpt will quickly  perhaps got accidentally killed).  In this case, fixpt will quickly
1502  move through what exists before continuing where it left off earlier,  move through what exists before continuing where it left off earlier,
1503  and, thus, saves a lot of time.  and, thus, saves a lot of time.
1504    
# Line 1148  Line 1548 
1548    it from that remote directory.    it from that remote directory.
1549    This should simplify installation further:  For machines that have    This should simplify installation further:  For machines that have
1550    access to the internet, just fetch <version>-config.tgz, unpack it,    access to the internet, just fetch <version>-config.tgz, unpack it,
1551    edit config/targets, and go (run config/install.sh).  The scipt will    edit config/targets, and go (run config/install.sh).  The script will
1552    fetch everything else that it might need all by itself.    fetch everything else that it might need all by itself.
1553    
1554    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.656  
changed lines
  Added in v.676

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