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 677, Mon Jun 26 00:56:56 2000 UTC revision 683, Wed Jul 5 00:42:19 2000 UTC
# Line 12  Line 12 
12  Tag: <post-commit CVS tag>  Tag: <post-commit CVS tag>
13  Description:  Description:
14  ----------------------------------------------------------------------  ----------------------------------------------------------------------
15    Name: Allen Leung
16    Date: 2000/06/15 00:38:00
17    Tag: leunga-20000704-sparc-x86
18    
19    1. x86 peephole improvement sp += k; sp -= k => nop  [from John]
20    2. fix to x86 RET bug [found by Dan Grossman]
21    3. sparc assembly bug fix for ticc instructions [found by Fermin]
22    
23       Affects c-- and moby only
24    
25    ----------------------------------------------------------------------
26    Name: Matthias Blume
27    Date: 2000/07/04 15:26:00
28    Tag: blume-20000704-trigger
29    Description:
30    
31    1. Improvements to CM manual.
32    2. SMLofNJ.Internals.BTrace.trigger reinstated as an alternative way
33       of getting a back-trace.  The function, when called, raises an
34       internal exception which explicitly carries the full back-trace history,
35       so it is unaffected by any intervening handle-raise pairs ("trivial"
36       or not).  The interactive loop will print that history once it arrives
37       at top level.
38       Short of having all exceptions implicitly carry the full history, the
39       recommended way of using this facility is:
40         - compile your program with instrumentation "on"
41         - run it, when it raises an exception, look at the history
42         - if the history is "cut off" because of some handler, go and modify
43           your program so that it explicitly calls BTrace.trigger
44         - recompile (still instrumented), and rerun; look at the full history
45    
46    ----------------------------------------------------------------------
47    Name: Matthias Blume
48    Date: 2000/07/03 15:36:00 JST
49    Tag: blume-20000702-manual
50    Description:
51    
52    Small corrections and updates to CM manual.
53    
54    ----------------------------------------------------------------------
55    Name: Matthias Blume
56    Date: 2000/06/29 16:04:00 JST
57    Tag: blume-20000629-yacctool
58    Description:
59    
60    Changes:
61    
62    1. Class "mlyacc" now takes separate arguments to pass options to
63       generated .sml- and .sig-files independently.
64    2. Corresponding CM manual updates.
65    3. BTrace module now also reports call sites.  (However, for loop clusters
66       it only shows from where the cluster was entered.)  There are associated
67       modifications to core.sml, internals.{sig,sml}, btrace.sml, and btimp.sml.
68    
69    ----------------------------------------------------------------------
70    Name: Matthias Blume
71    Date: 2000/06/27 16:51:00 JST
72    Tag: blume-20000627-noweb
73    Description:
74    
75    Changes:
76    
77     1. Implemented "subdir" and "witness" options for noweb tool.
78        This caused some slight internal changes in CM's tool implementation.
79     2. Fixed bug in "tool plugin" mechanism.  This is essentially cleaning
80        some remaining issues from earlier path anchor changes.
81     3. Updated CM manual accordingly.
82    
83     4. Changed implementation of back-tracing so that I now consider it
84        ready for prime-time.
85    
86        In particular, you don't have to explicitly trigger the back-trace
87        anymore.  Instead, if you are running BTrace-instrumented code and
88        there is an uncaught exception (regardless of whether or not it was
89        raised in instrumented code), the top-level evalloop will print
90        the back-trace.
91    
92        Features:
93    
94          - Instrumented and uninstrumented code work together seemlessly.
95            (Of course, uninstrumented code is never mentioned in actual
96             back-traces.)
97    
98          - Asymptotic time- and space-complexity of instrumented code is
99            equal to that of uninstrumented code.  (This means that
100            tail-recursion is preserved by the instrumentation phase.)
101    
102          - Modules whose code has been instrumented in different sessions
103            work together without problem.
104    
105          - There is no penalty whatsoever on uninstrumented code.
106    
107          - There is no penalty on "raise" expressions, even in
108            instrumented code.
109    
110        A potential bug (or perhaps it is a feature, too):
111    
112          A back-trace reaches no further than the outermost instrumented
113          non-trivial "raise".  Here, a "trivial" raise is one that is the
114          sole RHS of a "handle" rule.  Thus, back-traces reach trough
115    
116               <exp> handle e => raise e
117    
118          and even
119    
120               <exp> handle Foo => raise Bar
121    
122          and, of course, through
123    
124               <exp> handle Foo => ...
125    
126         if the exception was not Foo.
127    
128         Back-traces always reach right through any un-instrumented code
129         including any of its "handle" expressions, trivial or not.
130    
131       To try this out, do the following:
132    
133         - Erase all existing binfiles for your program.
134           (You may keep binfiles for those modules where you think you
135            definitely don't need back-tracing.)
136         - Turn on back-trace instrumentation:
137              SMLofNJ.Internals.BTrace.mode (SOME true);
138         - Recompile your program.  (I.e., run "CM.make" or "use".)
139         - You may now turn instrumentation off again (if you want):
140              SMLofNJ.Internals.BTrace.mode (SOME false);
141         - Run your program as usual.  If it raises an exception that
142           reaches the interactive toplevel, then a back-trace will
143           automatically be printed.  After that, the toplevel loop
144           will print the exception history as usual.
145    
146    ----------------------------------------------------------------------
147  Name: Matthias Blume  Name: Matthias Blume
148  Date: 2000/06/26 09:56:46 JST  Date: 2000/06/26 09:56:46 JST
149  Tag: blume-20000626-setup  Tag: blume-20000626-setup

Legend:
Removed from v.677  
changed lines
  Added in v.683

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