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

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

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