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

Legend:
Removed from v.676  
changed lines
  Added in v.684

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