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 646, Tue May 16 02:52:54 2000 UTC revision 673, Wed Jun 21 08:57:07 2000 UTC
# Line 12  Line 12 
12  Tag: <post-commit CVS tag>  Tag: <post-commit CVS tag>
13  Description:  Description:
14  ----------------------------------------------------------------------  ----------------------------------------------------------------------
15    Name: Matthias Blumen
16    Date: 2000/06/21 18:00:00 JST
17    Tag: blume-20000621-manual
18    Description:
19    
20    CM manual update: Path environments documented.
21    
22    ----------------------------------------------------------------------
23    Name: Matthias Blume
24    Date: 2000/06/19 13:40:00
25    Tag: blume-20000619-manual
26    Description:
27    
28    CM manual and system/README update.  This only covers the fact that
29    there are no more implicit anchors.  (Path environments and the "bind"
30    option to "cm" have yet to be documented.)
31    
32    ----------------------------------------------------------------------
33    Name: Matthias Blume
34    Date: 2000/06/19 11:05:00 JST
35    Tag: blume-20000619-chdir-bugfix
36    Description:
37    
38    Fixed a bug in new SrcPath module that sometimes led to a bad chDir call.
39    
40    ----------------------------------------------------------------------
41    Name: Matthias Blume
42    Date: 2000/06/18 22:00:10 JST
43    Tag: blume-20000618-implicit-anchors-really-gone
44    Description:
45    
46    I updates the previous HISTORY entry where I forgot to mention that
47    implicit anchors are no longer with us.
48    
49    The current update also gets rid of the (now useless) controller
50    CM.Control.implicit_anchors.
51    
52    ----------------------------------------------------------------------
53    Name: Matthias Blume
54    Date: 2000/06/16 17:30:00 JST
55    Tag: blume-20000616-anchorenv
56    Description:
57    
58    This patch implements the long anticipated (just kidding :) "anchor
59    environment" mechanism.  In the course of doing this, I also
60    re-implemented CM's internal "SrcPath" module from scratch.  The new
61    one should be more robust in certain boundary cases.  In any case, it
62    is a lot cleaner than its predecessor (IMHO).
63    
64    This time, although there is yet another boot file format change, I
65    kept the unpickler backward-compatible.  As a result, no new bootfiles
66    are necessary and bootstrapping is straightforward.  (You cannot read
67    new bootfiles into an old system, but the other way around is no
68    problem.)
69    
70    Visible changes:
71    
72    ** 0. Implicit path anchors (without the leading $-symbol) are no
73    longer recognized at all. This means that such path names are not
74    illegal either.  For example, the name basis.cm simply refers to a
75    local file called "basis.cm" (i.e, the name is an ordinary path
76    relative to .cm-files directory).  Or, to put it differently, only
77    names that start with $ are anchored paths.
78    
79    ** 1. The $<singlearc> abbreviation for $/<singlearc> has finally
80    vanished.
81    
82    John (Reppy) had critizised this as soon as I originally proposed and
83    implemented it, but at that time I did not really deeply believe
84    him. :) Now I came full-circle because I need the $<singlearc> syntax
85    in another place where it cannot be seen as an abbreviation for
86    $/<singlearc>.  To avoid the confusion, $<singlearc> now means what it
87    seems to mean (i.e., it "expands" into the corresponding anchor
88    value).
89    
90    However, when paths are used as members in CM description files, it
91    continues to be true that there must be at least another arc after the
92    anchor.  This is now enforced separately during semantic analysis
93    (i.e., from a lexical/syntactical point of view, the notation is ok.)
94    
95    ** 2. The "cm" class now accepts an option "bind".  The option's value
96    is a sub-option list of precisely two items -- one labeled "anchor"
97    and the other one labeled "value".  As you might expect, "anchor" is
98    used to specify an anchor name to be bound, and "value" specifies what
99    the anchor is being bound to.
100    
101    The value must be a directory name and can be given in either standard
102    syntax (including the possibility that it is itself an anchored path)
103    or native syntax.
104    
105    Examples:
106    
107       foo.cm (bind:(anchor:bar value:$mystuff/bar))
108       lib.cm (bind:(anchor:a value:"H:\\x\\y\\z"))  (* only works under windows *)
109    
110    and so on.
111    
112    The meaning of this is that the .cm-file will be processed with an
113    augmented anchor environment where the given anchor(s) is/are bound to
114    the given values(s).
115    
116    The rationale for having this feature is this: Suppose you are trying
117    to use two different (already stable) libraries a.cm and b.cm (that
118    you perhaps didn't write yourself).  Further, suppose each of these
119    two libraries internally uses its own auxiliary library $aux/lib.cm.
120    Normally you would now have a problem because the anchor "lib" can not
121    be bound to more than one value globally.  Therefore, the project that
122    uses both a.cm and b.cm must locally redirect the anchor to some other
123    place:
124    
125       a.cm (bind:(anchor:lib value:/usr/lib/smlnj/a-stuff))
126       b.cm (bind:(anchor:lib value:/usr/lib/smlnj/b-stuff))
127    
128    This hard-wires $lib/aux.cm to /usr/lib/smlnj/a-stuff/aux.cm or
129    /usr/lib/smlnj/b-stuff/aux.cm, respectively.
130    
131    Hard-wiring path names is a bit inflexible (and CM will verbosely warn
132    you when you do so at the time of CM.stabilize).  Therefore, you can
133    also use an anchored path as the value:
134    
135      a.cm (bind:(anchor:lib value:$a-lib))
136      b.cm (bind:(anchor:lib value:$b-lib))
137    
138    Now you can globally configure (using the usual CM.Anchor.anchor or
139    pathconfig machinery) bindings for "a-lib" and "b-lib".  Since "lib"
140    itself is always locally bound, setting it globally is no longer
141    meaningful or necessary (but it does not hurt either).  In fact, "lib"
142    can still be used as a global anchor for separate purposes.  As a
143    matter of fact, one can locally define "lib" in terms of a global
144    "lib":
145    
146      a.cm (bind:(anchor:lib value:$lib/a))
147      b.cm (bind:(anchor:lib value:$lib/b))
148    
149    ** 3: The encoding of path names has changed.  This affects the way
150    path names are shown in CM's progress report and also the internal
151    protocol encoding used for parallel make.
152    
153    The encoding now uses one or more ':'-separated segments.  Each
154    segments corresponds to a file that has been specified relative to the
155    file given by its preceding segment.  The first segment is either
156    relative to the CWD, absolute, or anchored.  Each segment itself is
157    basically a Unix pathname; all segments but the first are relative.
158    
159    Example:
160    
161       $foo/bar/baz.cm:a/b/c.sml
162    
163    This path denotes the file bar/a/b/c.sml relative to the directory
164    denoted by anchor "foo".  Notice that the encoding also includes
165    baz.cm which is the .cm-file that listed a/b/c.sml.  As usual, such
166    paths are resolved relative to the .cm-files directory, so baz.cm must
167    be ignored to get the "real" pathname.
168    
169    To make this fact more obvious, CM puts the names of such "virtual
170    arcs" into parentheses when they appear in progress reports. (No
171    parentheses will appear in the internal protocol encoding.)  Thus,
172    what you really see is:
173    
174      $foo/bar/(baz.cm):a/b/c.sml
175    
176    I find this notation to be much more informative than before.
177    
178    Another new feature of the encoding is that special characters
179    including parentheses, colons, (back)slashes, and white space are
180    written as \ddd (where ddd is the decimal encoding of the character).
181    
182    *** The CM manual still needs to be updated.
183    
184    ----------------------------------------------------------------------
185    Name: Allen Leung
186    Date: 2000/06/15 00:38:00
187    Tag: leunga-20000615-x86-peephole
188    
189    x86 Peephole fix by Fermin.  Affects c-- and moby only.
190    
191    ----------------------------------------------------------------------
192    Name: Matthias Blume
193    Date: 2000/06/12 11:40:00
194    Tag: blume-20000612-parmakefix
195    Description:
196    
197    More cleanup after changing the file naming scheme: This time I
198    repaired the parallel make mechanism for CMB.make which I broke earlier.
199    
200    ----------------------------------------------------------------------
201    Name: Allen Leung
202    Date: 2000/06/09 01:25:00
203    Tag: leunga-20000609-various
204    
205    None of these things should affect normal SML/NJ operations
206    
207    1. Peephole improvements provided by Fermin (c--)
208    2. New annotation DEFUSE for adding extra dependence (moby)
209    3. New X86 LOCK instructions (moby)
210    4. New machine description language for reservation tables (scheduling)
211    5. Fixes to various optimization/analysis modules (branch chaining, dominator
212       trees etc.)
213    6. I've changed the CM files so that they can work with versions
214       110.0.6, 110.25 and 110.28
215    
216    ----------------------------------------------------------------------
217    Name: Matthias Blume
218    Date: 2000/06/09 12:40:00
219    Tag: blume-20000609-log
220    Description:
221    
222    - Removed all(?) remaining RCS Log entries from sources.
223    
224    - Fixed bug in ml-yacc and ml-lex sources (use explicit anchors for
225      anchored paths).
226    
227    ----------------------------------------------------------------------
228    Name: Matthias Blume
229    Date: 2000/06/07 17:00:00 JST
230    Tag: blume-20000607-no-implicit-anchors
231    Description:
232    
233    1. This update changes the default setting for
234    CM.Control.implicit_anchors from true to false.  This means that
235    implicit anchors are no longer permitted by default.  I also tried to
236    make sure that nothing else still relies on implicit anchors.
237    (This is the next step on the schedule towards a CM that does not even
238    have the notion of implicit anchors anymore.)
239    
240    2. More CM manual updates.
241    
242    3. I managed to track down and fix the pickling bug I mentioned last
243    time.  Because of the previously existing workaround, this entails no
244    immediate practical changes.
245    
246    ----------------------------------------------------------------------
247    Name: Matthias Blume
248    Date: 2000/06/06 11:15:00 JST
249    Tag: blume-20000606-lazierpickle
250    Description:
251    
252    !!!! NEW BOOT FILES !!!!
253    
254    * The main purpose of this update is to make library pickles lazier in
255    order to reduce the initial space penalty for autoloading a library.
256    As a result, it is now possible to have $smlnj/compiler.cm
257    pre-registered.  This should take care of the many complaints or
258    inquiries about missing structure Compiler.  This required changes to
259    CM's internal data structures and small tweaks to some algorithms.
260    
261    As a neat additional effect, it is no longer necessary (for the sake
262    of lean heap image files) to distinguish between a "minimal" CM and a
263    "full" CM.  Now, there is only one CM (i.e., the "full" version:
264    $smlnj/cm.cm aka $smlnj/cm/full.cm), and it is always available at the
265    interactive top level. ($smlnj/cm/minimal.cm is gone.)
266    
267    To make the life of compiler-hackers easier, "makeml" now also
268    pre-registers $smlnj/cmb.cm (aka $smlnj/cmb/current.cm).  In other
269    words, after you bootstrap a new sml for the first time, you will not
270    have to autoload $smlnj/cmb.cm again afterwards.  (The first time
271    around you will still have to do it, though.)
272    
273    * A second change consists of major updates to the CM manual.  There
274    are now several appendices with summary information and also a full
275    specification of the CM description file syntax.
276    
277    * In directory src/system I added the script "allcross".  This script
278    invokes sml and cross-compiles the compiler for all supported
279    architectures.  (Useful when providing a new set of boot files.)
280    
281    * There seems to be a latent bug in my "lazy pickles" mechanism.  I
282    added a small tweak to pickle-util.sml to work around this problem,
283    but it is not a proper fix yet.  I will investigate further.  (The
284    effect of the bug was an inflation of library pickle size.)
285    
286    * Version number increased to 110.28.1 (to avoid compatibility problems).
287    
288    ----------------------------------------------------------------------
289    Name: Allen Leung
290    Date: 2000/05/25 17:28 EDT
291    Tag: leunga-20000525-ra
292    Description:
293    
294      Fixed a bug in freezing phase of the register allocator.
295    
296    ----------------------------------------------------------------------
297  Name: Allen Leung  Name: Allen Leung
298  Date: 2000/05/15 16:02 EDT  Date: 2000/05/15 22:53 EDT
299  Tag: leunga-20000515-alpha-x86-ra  Tag: leunga-20000515-alpha-x86-ra
300  Description:  Description:
301    
# Line 33  Line 315 
315    
316        The module ra-rewrite-with-renaming has been improved.        The module ra-rewrite-with-renaming has been improved.
317    
318      These have no effect on SML/NJ.
319    
320  ----------------------------------------------------------------------  ----------------------------------------------------------------------
321  Name: Matthias Blume  Name: Matthias Blume
322  Date: 2000/05/15 16:20:00 JST  Date: 2000/05/15 16:20:00 JST
# Line 492  Line 776 
776    
777  3.  Assembly  3.  Assembly
778    
779      When generating assemby, resolve the value of client defined constants,      When generating assembly, resolve the value of client defined constants,
780      instead of generating symbolic values.  This is controlled by the      instead of generating symbolic values.  This is controlled by the
781      new flag "asm-resolve-constants", which is default to true.      new flag "asm-resolve-constants", which is default to true.
782    
# Line 515  Line 799 
799    
800  To this end, I arranged that instead of "structure Core" as "structure  To this end, I arranged that instead of "structure Core" as "structure
801  _Core" is bound in the pervasive environment.  Core access is done via  _Core" is bound in the pervasive environment.  Core access is done via
802  _Core (which can never be accidentially rebound because _Core is not a  _Core (which can never be accidentally rebound because _Core is not a
803  legal surface-syntax symbol).  legal surface-syntax symbol).
804    
805  The current solution is much cleaner because the core environment is  The current solution is much cleaner because the core environment is
# Line 525  Line 809 
809  with dynamic and symbolic parts of the core environment.  with dynamic and symbolic parts of the core environment.
810    
811  Remaining hackery (to bind the "magic" symbol _Core) is localized in the  Remaining hackery (to bind the "magic" symbol _Core) is localized in the
812  compilation mananger's bootstrap compiler (actually: in the "init group"  compilation manager's bootstrap compiler (actually: in the "init group"
813  handling).  See the comments in src/system/smlnj/init/init.cmi for  handling).  See the comments in src/system/smlnj/init/init.cmi for
814  more details.  more details.
815    
# Line 640  Line 924 
924     (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
925     used).     used).
926    
927     This was done to accomodate the new "make" and "shell" tools which     This was done to accommodate the new "make" and "shell" tools which
928     facilitate fairly seemless hookup to portions of code managed using     facilitate fairly seamless hookup to portions of code managed using
929     Makefiles or Shell scripts.     Makefiles or Shell scripts.
930    
931     There are no classes "shared" or "private" anymore.  Instead, the     There are no classes "shared" or "private" anymore.  Instead, the
# Line 653  Line 937 
937    
938     All existing tools are described in the CM manual.     All existing tools are described in the CM manual.
939    
940     - Slightly better error handling.  (CM now surpresses many followup     - Slightly better error handling.  (CM now suppresses many followup
941     error messages that tended to be more annoying than helpful.)     error messages that tended to be more annoying than helpful.)
942    
943  2. Major changes to the compiler's static environment data structures.  2. Major changes to the compiler's static environment data structures.
# Line 787  Line 1071 
1071    
1072       I've changed andl to testl in the floating point test sequence       I've changed andl to testl in the floating point test sequence
1073       whenever appropriate.  The Intel optimization guide states that       whenever appropriate.  The Intel optimization guide states that
1074       testl is perferable to andl.       testl is preferable to andl.
1075    
1076  7. RA (x86 only)  7. RA (x86 only)
1077    
# Line 969  Line 1253 
1253    
1254  1. Tools.registerStdShellCmdTool (from smlnj/cm/tool.cm) takes an  1. Tools.registerStdShellCmdTool (from smlnj/cm/tool.cm) takes an
1255  additional argument called "template" which is an optional string that  additional argument called "template" which is an optional string that
1256  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
1257  explanation.  explanation.
1258    
1259  2. A special-purpose tool can be "regisitered" by simply dropping the  2. A special-purpose tool can be "registered" by simply dropping the
1260  corresponding <...>-tool.cm (and/or <...>-ext.cm) into the same  corresponding <...>-tool.cm (and/or <...>-ext.cm) into the same
1261  directory where the .cm file lives that uses this tool.  (The  directory where the .cm file lives that uses this tool.  (The
1262  behavior/misfeature until now was to look for the tool description  behavior/misfeature until now was to look for the tool description
# Line 1016  Line 1300 
1300  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
1301  <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,
1302  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
1303  perhaps got accidentially killed).  In this case, fixpt will quickly  perhaps got accidentally killed).  In this case, fixpt will quickly
1304  move through what exists before continuing where it left off earlier,  move through what exists before continuing where it left off earlier,
1305  and, thus, saves a lot of time.  and, thus, saves a lot of time.
1306    
# Line 1066  Line 1350 
1350    it from that remote directory.    it from that remote directory.
1351    This should simplify installation further:  For machines that have    This should simplify installation further:  For machines that have
1352    access to the internet, just fetch <version>-config.tgz, unpack it,    access to the internet, just fetch <version>-config.tgz, unpack it,
1353    edit config/targets, and go (run config/install.sh).  The scipt will    edit config/targets, and go (run config/install.sh).  The script will
1354    fetch everything else that it might need all by itself.    fetch everything else that it might need all by itself.
1355    
1356    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.646  
changed lines
  Added in v.673

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