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 648, Thu May 25 21:28:21 2000 UTC revision 666, Fri Jun 16 08:27:00 2000 UTC
# Line 12  Line 12 
12  Tag: <post-commit CVS tag>  Tag: <post-commit CVS tag>
13  Description:  Description:
14  ----------------------------------------------------------------------  ----------------------------------------------------------------------
15    Name: Matthias Blume
16    Date: 2000/06/16 17:30:00 JST
17    Tag: blume-20000616-anchorenv
18    Description:
19    
20    This patch implements the long anticipated (just kidding :) "anchor
21    environment" mechanism.  In the course of doing this, I also
22    re-implemented CM's internal "SrcPath" module from scratch.  The new
23    one should be more robust in certain boundary cases.  In any case, it
24    is a lot cleaner than its predecessor (IMHO).
25    
26    This time, although there is yet another boot file format change, I
27    kept the unpickler backward-compatible.  As a result, no new bootfiles
28    are necessary and bootstrapping is straightforward.  (You cannot read
29    new bootfiles into an old system, but the other way around is no
30    problem.)
31    
32    Visible changes:
33    
34    ** 1. The $<singlearc> abbreviation for $/<singlearc> for anchored
35    paths has finally vanished.
36    
37    John had critizised this as soon as I originally proposed and
38    implemented it, but at that time I did not really deeply believe
39    him. :) Now I came full-circle because I need the $<singlearc> syntax
40    in another place where it cannot be seen as an abbreviation for
41    $/<singlearc>.  To avoid the confusion, $<singlearc> now means what it
42    seems to mean (i.e., it "expands" into the corresponding anchor
43    value).
44    
45    However, when paths are used as members in CM description files, it
46    continues to be true that there must be at least another arc after the
47    anchor.  This is now enforced separately during semantic analysis
48    (i.e., form a lexical/syntactical point of view, the notation is ok.)
49    
50    ** 2. The "cm" class now accepts an option "bind".  The option's value
51    is a sub-option list of precisely two items -- one labeled "anchor"
52    and the other one labeled "value".  As you might expect, "anchor" is
53    used to specify an anchor name to be bound, and "value" specifies what
54    the anchor is being bound to.
55    
56    The value must be a directory name and can be given in either standard
57    syntax (including the possibility that it is itself an anchored path)
58    or native syntax.
59    
60    Examples:
61    
62       foo.cm (bind:(anchor:bar value:$mystuff/bar))
63       lib.cm (bind:(anchor:a value:"H:\\x\\y\\z"))  (* only works under windows *)
64    
65    and so on.
66    
67    The meaning of this is that the .cm-file will be processed with an
68    augmented anchor environment where the given anchor(s) is/are bound to
69    the given values(s).
70    
71    The rationale for having this feature is this: Suppose you are trying
72    to use two different (already stable) libraries a.cm and b.cm (that
73    you perhaps didn't write yourself).  Further, suppose each of these
74    two libraries internally uses its own auxiliary library $aux/lib.cm.
75    Normally you would now have a problem because the anchor "lib" can not
76    be bound to more than one value globally.  Therefore, the project that
77    uses both a.cm and b.cm must locally redirect the anchor to some other
78    place:
79    
80       a.cm (bind:(anchor:lib value:/usr/lib/smlnj/a-stuff))
81       b.cm (bind:(anchor:lib value:/usr/lib/smlnj/b-stuff))
82    
83    This hard-wires $lib/aux.cm to /usr/lib/smlnj/a-stuff/aux.cm or
84    /usr/lib/smlnj/b-stuff/aux.cm, respectively.
85    
86    Hard-wiring path names is a bit inflexible (and CM will verbosely warn
87    you when you do so at the time of CM.stabilize).  Therefore, you can
88    also use an anchored path as the value:
89    
90      a.cm (bind:(anchor:lib value:$a-lib))
91      b.cm (bind:(anchor:lib value:$b-lib))
92    
93    Now you can globally configure (using the usual CM.Anchor.anchor or
94    pathconfig machinery) bindings for "a-lib" and "b-lib".  Since "lib"
95    itself is always locally bound, setting it globally is no longer
96    meaningful or necessary (but it does not hurt either).  In fact, "lib"
97    can still be used as a global anchor for separate purposes.  As a
98    matter of fact, one can locally define "lib" in terms of a global
99    "lib":
100    
101      a.cm (bind:(anchor:lib value:$lib/a))
102      b.cm (bind:(anchor:lib value:$lib/b))
103    
104    ** 3: The encoding of path names has changed.  This affects the way
105    path names are shown in CM's progress report and also the internal
106    protocol encoding used for parallel make.
107    
108    The encoding now uses one or more ':'-separated segments.  Each
109    segments corresponds to a file that has been specified relative to the
110    file given by its preceding segment.  The first segment is either
111    relative to the CWD, absolute, or anchored.  Each segment itself is
112    basically a Unix pathname; all segments but the first are relative.
113    
114    Example:
115    
116       $foo/bar/baz.cm:a/b/c.sml
117    
118    This path denotes the file bar/a/b/c.sml relative to the directory
119    denoted by anchor "foo".  Notice that the encoding also includes
120    baz.cm which is the .cm-file that listed a/b/c.sml.  As usual, such
121    paths are resolved relative to the .cm-files directory, so baz.cm must
122    be ignored to get the "real" pathname.
123    
124    To make this fact more obvious, CM puts the names of such "virtual
125    arcs" into parentheses when they appear in progress reports. (No
126    parentheses will appear in the internal protocol encoding.)  Thus,
127    what you really see is:
128    
129      $foo/bar/(baz.cm):a/b/c.sml
130    
131    I find this notation to be much more informative than before.
132    
133    Another new feature of the encoding is that special characters
134    including parentheses, colons, (back)slashes, and white space are
135    written as \ddd (where ddd is the decimal encoding of the character).
136    
137    ----------------------------------------------------------------------
138    Name: Allen Leung
139    Date: 2000/06/15 00:38:00
140    Tag: leunga-20000615-x86-peephole
141    
142    x86 Peephole fix by Fermin.  Affects c-- and moby only.
143    
144    ----------------------------------------------------------------------
145    Name: Matthias Blume
146    Date: 2000/06/12 11:40:00
147    Tag: blume-20000612-parmakefix
148    Description:
149    
150    More cleanup after changing the file naming scheme: This time I
151    repaired the parallel make mechanism for CMB.make which I broke earlier.
152    
153    ----------------------------------------------------------------------
154    Name: Allen Leung
155    Date: 2000/06/09 01:25:00
156    Tag: leunga-20000609-various
157    
158    None of these things should affect normal SML/NJ operations
159    
160    1. Peephole improvements provided by Fermin (c--)
161    2. New annotation DEFUSE for adding extra dependence (moby)
162    3. New X86 LOCK instructions (moby)
163    4. New machine description language for reservation tables (scheduling)
164    5. Fixes to various optimization/analysis modules (branch chaining, dominator
165       trees etc.)
166    6. I've changed the CM files so that they can work with versions
167       110.0.6, 110.25 and 110.28
168    
169    ----------------------------------------------------------------------
170    Name: Matthias Blume
171    Date: 2000/06/09 12:40:00
172    Tag: blume-20000609-log
173    Description:
174    
175    - Removed all(?) remaining RCS Log entries from sources.
176    
177    - Fixed bug in ml-yacc and ml-lex sources (use explicit anchors for
178      anchored paths).
179    
180    ----------------------------------------------------------------------
181    Name: Matthias Blume
182    Date: 2000/06/07 17:00:00 JST
183    Tag: blume-20000607-no-implicit-anchors
184    Description:
185    
186    1. This update changes the default setting for
187    CM.Control.implicit_anchors from true to false.  This means that
188    implicit anchors are no longer permitted by default.  I also tried to
189    make sure that nothing else still relies on implicit anchors.
190    (This is the next step on the schedule towards a CM that does not even
191    have the notion of implicit anchors anymore.)
192    
193    2. More CM manual updates.
194    
195    3. I managed to track down and fix the pickling bug I mentioned last
196    time.  Because of the previously existing workaround, this entails no
197    immediate practical changes.
198    
199    ----------------------------------------------------------------------
200    Name: Matthias Blume
201    Date: 2000/06/06 11:15:00 JST
202    Tag: blume-20000606-lazierpickle
203    Description:
204    
205    !!!! NEW BOOT FILES !!!!
206    
207    * The main purpose of this update is to make library pickles lazier in
208    order to reduce the initial space penalty for autoloading a library.
209    As a result, it is now possible to have $smlnj/compiler.cm
210    pre-registered.  This should take care of the many complaints or
211    inquiries about missing structure Compiler.  This required changes to
212    CM's internal data structures and small tweaks to some algorithms.
213    
214    As a neat additional effect, it is no longer necessary (for the sake
215    of lean heap image files) to distinguish between a "minimal" CM and a
216    "full" CM.  Now, there is only one CM (i.e., the "full" version:
217    $smlnj/cm.cm aka $smlnj/cm/full.cm), and it is always available at the
218    interactive top level. ($smlnj/cm/minimal.cm is gone.)
219    
220    To make the life of compiler-hackers easier, "makeml" now also
221    pre-registers $smlnj/cmb.cm (aka $smlnj/cmb/current.cm).  In other
222    words, after you bootstrap a new sml for the first time, you will not
223    have to autoload $smlnj/cmb.cm again afterwards.  (The first time
224    around you will still have to do it, though.)
225    
226    * A second change consists of major updates to the CM manual.  There
227    are now several appendices with summary information and also a full
228    specification of the CM description file syntax.
229    
230    * In directory src/system I added the script "allcross".  This script
231    invokes sml and cross-compiles the compiler for all supported
232    architectures.  (Useful when providing a new set of boot files.)
233    
234    * There seems to be a latent bug in my "lazy pickles" mechanism.  I
235    added a small tweak to pickle-util.sml to work around this problem,
236    but it is not a proper fix yet.  I will investigate further.  (The
237    effect of the bug was an inflation of library pickle size.)
238    
239    * Version number increased to 110.28.1 (to avoid compatibility problems).
240    
241    ----------------------------------------------------------------------
242  Name: Allen Leung  Name: Allen Leung
243  Date: 2000/05/25 17:28 EDT  Date: 2000/05/25 17:28 EDT
244  Tag: leunga-20000525-ra  Tag: leunga-20000525-ra
# Line 502  Line 729 
729    
730  3.  Assembly  3.  Assembly
731    
732      When generating assemby, resolve the value of client defined constants,      When generating assembly, resolve the value of client defined constants,
733      instead of generating symbolic values.  This is controlled by the      instead of generating symbolic values.  This is controlled by the
734      new flag "asm-resolve-constants", which is default to true.      new flag "asm-resolve-constants", which is default to true.
735    
# Line 525  Line 752 
752    
753  To this end, I arranged that instead of "structure Core" as "structure  To this end, I arranged that instead of "structure Core" as "structure
754  _Core" is bound in the pervasive environment.  Core access is done via  _Core" is bound in the pervasive environment.  Core access is done via
755  _Core (which can never be accidentially rebound because _Core is not a  _Core (which can never be accidentally rebound because _Core is not a
756  legal surface-syntax symbol).  legal surface-syntax symbol).
757    
758  The current solution is much cleaner because the core environment is  The current solution is much cleaner because the core environment is
# Line 535  Line 762 
762  with dynamic and symbolic parts of the core environment.  with dynamic and symbolic parts of the core environment.
763    
764  Remaining hackery (to bind the "magic" symbol _Core) is localized in the  Remaining hackery (to bind the "magic" symbol _Core) is localized in the
765  compilation mananger's bootstrap compiler (actually: in the "init group"  compilation manager's bootstrap compiler (actually: in the "init group"
766  handling).  See the comments in src/system/smlnj/init/init.cmi for  handling).  See the comments in src/system/smlnj/init/init.cmi for
767  more details.  more details.
768    
# Line 650  Line 877 
877     (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
878     used).     used).
879    
880     This was done to accomodate the new "make" and "shell" tools which     This was done to accommodate the new "make" and "shell" tools which
881     facilitate fairly seemless hookup to portions of code managed using     facilitate fairly seamless hookup to portions of code managed using
882     Makefiles or Shell scripts.     Makefiles or Shell scripts.
883    
884     There are no classes "shared" or "private" anymore.  Instead, the     There are no classes "shared" or "private" anymore.  Instead, the
# Line 663  Line 890 
890    
891     All existing tools are described in the CM manual.     All existing tools are described in the CM manual.
892    
893     - Slightly better error handling.  (CM now surpresses many followup     - Slightly better error handling.  (CM now suppresses many followup
894     error messages that tended to be more annoying than helpful.)     error messages that tended to be more annoying than helpful.)
895    
896  2. Major changes to the compiler's static environment data structures.  2. Major changes to the compiler's static environment data structures.
# Line 797  Line 1024 
1024    
1025       I've changed andl to testl in the floating point test sequence       I've changed andl to testl in the floating point test sequence
1026       whenever appropriate.  The Intel optimization guide states that       whenever appropriate.  The Intel optimization guide states that
1027       testl is perferable to andl.       testl is preferable to andl.
1028    
1029  7. RA (x86 only)  7. RA (x86 only)
1030    
# Line 979  Line 1206 
1206    
1207  1. Tools.registerStdShellCmdTool (from smlnj/cm/tool.cm) takes an  1. Tools.registerStdShellCmdTool (from smlnj/cm/tool.cm) takes an
1208  additional argument called "template" which is an optional string that  additional argument called "template" which is an optional string that
1209  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
1210  explanation.  explanation.
1211    
1212  2. A special-purpose tool can be "regisitered" by simply dropping the  2. A special-purpose tool can be "registered" by simply dropping the
1213  corresponding <...>-tool.cm (and/or <...>-ext.cm) into the same  corresponding <...>-tool.cm (and/or <...>-ext.cm) into the same
1214  directory where the .cm file lives that uses this tool.  (The  directory where the .cm file lives that uses this tool.  (The
1215  behavior/misfeature until now was to look for the tool description  behavior/misfeature until now was to look for the tool description
# Line 1026  Line 1253 
1253  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
1254  <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,
1255  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
1256  perhaps got accidentially killed).  In this case, fixpt will quickly  perhaps got accidentally killed).  In this case, fixpt will quickly
1257  move through what exists before continuing where it left off earlier,  move through what exists before continuing where it left off earlier,
1258  and, thus, saves a lot of time.  and, thus, saves a lot of time.
1259    
# Line 1076  Line 1303 
1303    it from that remote directory.    it from that remote directory.
1304    This should simplify installation further:  For machines that have    This should simplify installation further:  For machines that have
1305    access to the internet, just fetch <version>-config.tgz, unpack it,    access to the internet, just fetch <version>-config.tgz, unpack it,
1306    edit config/targets, and go (run config/install.sh).  The scipt will    edit config/targets, and go (run config/install.sh).  The script will
1307    fetch everything else that it might need all by itself.    fetch everything else that it might need all by itself.
1308    
1309    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.648  
changed lines
  Added in v.666

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