Diff of /sml/trunk/HISTORY

Parent Directory | Revision Log | Patch

	revision 607, Mon Apr 10 16:31:03 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
148		Date: 2000/06/26 09:56:46 JST
149		Tag: blume-20000626-setup
150		Description:
151
152		CM: - setup-parameter to "sml" added; this can be used to run arbitrary
153		ML code before and after compiling a file (e.g., to set compiler
154		flags)
155
156		Compiler: - improved btrace API (in core.sml, internals.{sig,sml})
157		- associated changes to btrace.sml (BTrace instrumentation pass)
158		- cleaner implementation of btimp.sml (BTrace tracing and report
159		module)
160
161		CM manual: * new path encoding documented
162		* description of setup-parameter to "sml" added
163
164		The biggest user-visible change to back-tracing is that it is no
165		longer necessary to compile all traced modules within the same
166		session.  (This was a real limitation.)
167
168		----------------------------------------------------------------------
169		Name: Matthias Blume
170		Date: 2000/06/24 12:40:00 JST
171		Tag: blume-20000624-startup
172		Description:
173
174		Fixes startup slowdown problem.  (I was calling SrcPath.sync a _tad_
175		bit too often -- to put it mildly. :)
176
177		----------------------------------------------------------------------
178		Name: Matthias Blume
179		Date: 2000/06/23 18:20:00 JST
180		Tag: blume-20000623-btrace
181		Description:
182
183		This updates adds a backtrace facility to aid programmers in debugging
184		their programs.  This involves the following changes:
185
186		1. Module system/smlnj/init/core.sml (structure _Core) now has hooks for
187		keeping track of the current call stack.  When programs are compiled
188		in a special mode, the compiler will insert calls to these hooks
189		into the user program.
190		"Hook" means that it is possible for different implementations of
191		back-tracing to register themselves (at different times).
192
193		2. compiler/MiscUtil/profile/btrace.sml implements the annotation phase
194		as an Absyn.dec->Absyn.dec rewrite.  Normally this phase is turned off.
195		It can be turned on using this call:
196		SMLofNJ.Internals.BTrace.mode (SOME true);
197		Turning it off again:
198		SMLofNJ.Internals.BTrace.mode (SOME false);
199		Querying the current status:
200		SMLofNJ.Internals.BTrace.mode NONE;
201		Annotated programs are about twice as big as normal ones, and they
202		run a factor of 2 to 4 slower with a dummy back-trace plugin (one
203		where all hooks do nothing).  The slowdown with a plugin that is
204		actually useful (such as the one supplied by default) is even greater,
205		but in the case of the default plugin it is still only an constant
206		factor (amortized).
207
208		3. system/Basis/Implementation/NJ/internals.{sig,sml} have been augmented
209		with a sub-structure BTrace for controlling back-tracing.  In particular,
210		the above-mentioned function "mode" controls whether the annotation
211		phase is invoked by the compiler.  Another important function is
212		"trigger": when called it aborts the current execution and causes
213		the top-level loop to print a full back-trace.
214
215		4. compiler/MiscUtil/profile/btimp.sml is the current default plugin
216		for back-tracing.  It keeps track of the dynamic call stack and in
217		addition to that it keeps a partial history at each "level" of that
218		stack.  For example, if a tail-calls b, b tail-calls c, and c tail-calls
219		d and b (at separate times, dynamically), then the report will show:
220
221		GOTO   d
222		/c
223		GOTO  \b
224		CALL   a
225
226		This shows that there was an initial non-tail call of a, then a
227		tail-call to b or c, looping behavior in a cluster of functions that
228		consist of b and c, and then a goto from that cluster (i.e., either from
229		b or from c) to d.
230
231		Note that (depending on the user program) the amount of information
232		that the back-trace module has to keep track of at each level is bounded
233		by a constant.  Thus, the whole implementation has the same asymptotical
234		complexity as the original program (both in space and in time).
235
236		5. compiler/TopLevel/interact/evalloop.sml has been modified to
237		handle the special exception SMLofNJ.Internals.BTrace.BTrace
238		which is raised by the "trigger" function mentioned above.
239
240		Notes on usage:
241
242		- Annotated code works well together with unannotated code:
243		Unannotated calls simply do not show up at all in the backtrace.
244
245		- It is not a good idea to let modules that were annotated during
246		different sessions run at the same time.  This is because the compiler
247		chooses small integers to identify individual functions, and there
248		will be clashes if different modules were compiled in separate sessions.
249		(Nothing will crash, and you will even be told about the clashes, but
250		back-trace information will in general not be useful.)
251
252		- Back-tracing can be confused by callcc and capture.
253
254		- The only way of getting a back-trace right now is to explicitly
255		invoke the "trigger" function from your user program.  Eventually, we
256		should make every exception carry back-trace information (if
257		available).  But since this creates more overhead at "raise"-time
258		(similar to the current exnHistory overhead), I have not yet
259		implemented this.  (The implementation will be rather easy.)  With
260		exceptions carrying back-trace information, this facility will be even
261		more useful because users don't need to modify their programs...
262
263		- While it is possible to compile the compiler with back-trace
264		annotations turned on (I did it to get some confidence in
265		correctness), you must make absolutely sure that core.sml and
266		btimp.sml are compiled WITHOUT annotation!  (core.sml cannot actually
267		be compiled with annotation because there is no core access yet, but
268		if you compile btimp.sml with annotation, then the system will go into
269		an infinite recursion and crash.)
270		Since CM currently does not know about BTrace, the only way to turn
271		annotations on and off for different modules of the compiler is to
272		interrupt CMB.make, change the settings, and re-invoke it.  Of course,
273		this is awkward and clumsy.
274
275		Sample sessions:
276
277		Standard ML of New Jersey v110.28.1 [FLINT v1.5], June 5, 2000
278		- SMLofNJ.Internals.BTrace.mode (SOME true);
279		[autoloading]
280		[autoloading done]
281		val it = false : bool
282		- structure X = struct
283		-     fun main n = let
284		-         fun a (x, 0) = d x
285		-           | a (x, n) = b (x, n - 1)
286		-         and b (x, n) = c (x, n)
287		-         and c (x, n) = a (x, n)
288		-         and d x = e (x, 3)
289		-         and e (x, 0) = f x
290		-           | e (x, n) = e (x, n - 1)
291		-         and f 0 = SMLofNJ.Internals.BTrace.trigger ()
292		-           | f n = n * g (n - 1)
293		-         and g n = a (n, 3)
294		-     in
295		-         f n
296		-     end
297		- end;
298		structure X : sig val main : int -> int end
299		- X.main 3;
300		*** BACK-TRACE ***
301		GOTO   stdIn:4.2-13.20: X.main[2].f
302		GOTO-( stdIn:4.2-13.20: X.main[2].e
303		GOTO   stdIn:4.2-13.20: X.main[2].d
304		/ stdIn:4.2-13.20: X.main[2].a
305		| stdIn:4.2-13.20: X.main[2].b
306		GOTO-\ stdIn:4.2-13.20: X.main[2].c
307		CALL   stdIn:4.2-13.20: X.main[2].g
308		GOTO   stdIn:4.2-13.20: X.main[2].f
309		GOTO-( stdIn:4.2-13.20: X.main[2].e
310		GOTO   stdIn:4.2-13.20: X.main[2].d
311		/ stdIn:4.2-13.20: X.main[2].a
312		| stdIn:4.2-13.20: X.main[2].b
313		GOTO-\ stdIn:4.2-13.20: X.main[2].c
314		CALL   stdIn:4.2-13.20: X.main[2].g
315		GOTO   stdIn:4.2-13.20: X.main[2].f
316		GOTO-( stdIn:4.2-13.20: X.main[2].e
317		GOTO   stdIn:4.2-13.20: X.main[2].d
318		/ stdIn:4.2-13.20: X.main[2].a
319		| stdIn:4.2-13.20: X.main[2].b
320		GOTO-\ stdIn:4.2-13.20: X.main[2].c
321		CALL   stdIn:4.2-13.20: X.main[2].g
322		GOTO   stdIn:4.2-13.20: X.main[2].f
323		CALL   stdIn:2.15-17.4: X.main[2]
324		-
325
326		(Note that because of a FLINt bug the above code currently does not
327		compile without BTrace turned on.)
328
329		Here is another example, using my modified Tiger compiler:
330
331		Standard ML of New Jersey v110.28.1 [FLINT v1.5], June 5, 2000
332		- SMLofNJ.Internals.BTrace.mode (SOME true);
333		[autoloading]
334		[autoloading done]
335		val it = false : bool
336		- CM.make "sources.cm";
337		[autoloading]
338		...
339		[autoloading done]
340		[scanning sources.cm]
341		[parsing (sources.cm):parse.sml]
342		[creating directory CM/SKEL ...]
343		[parsing (sources.cm):tiger.lex.sml]
344		...
345		[wrote CM/sparc-unix/semant.sml]
346		[compiling (sources.cm):main.sml]
347		[wrote CM/sparc-unix/main.sml]
348		[New bindings added.]
349		val it = true : bool
350		- Main.compile ("../testcases/merge.tig", "foo.out");
351		*** BACK-TRACE ***
352		CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trvar
353		CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
354		CALL   lib/semant.sml:289.3-295.22: SemantFun[2].transExp.trexp.check[2]
355		GOTO   lib/semant.sml:289.3-295.22: SemantFun[2].transExp.trexp.check[2]
356		CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
357		CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
358		CALL   lib/semant.sml:488.3-505.6: SemantFun[2].transDec.trdec[2].transBody[2]
359		/ lib/semant.sml:411.65-543.8: SemantFun[2].transDec
360		CALL-\ lib/semant.sml:413.2-540.9: SemantFun[2].transDec.trdec[2]
361		CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
362		CALL   lib/semant.sml:8.52-558.4: SemantFun[2].transProg[2]
363		CALL   main.sml:1.18-118.4: Main.compile[2]
364		-
365
366		----------------------------------------------------------------------
367		Name: Matthias Blumen
368		Date: 2000/06/21 18:00:00 JST
369		Tag: blume-20000621-manual
370		Description:
371
372		CM manual update: Path environments documented.
373
374		----------------------------------------------------------------------
375		Name: Matthias Blume
376		Date: 2000/06/19 13:40:00
377		Tag: blume-20000619-manual
378		Description:
379
380		CM manual and system/README update.  This only covers the fact that
381		there are no more implicit anchors.  (Path environments and the "bind"
382		option to "cm" have yet to be documented.)
383
384		----------------------------------------------------------------------
385		Name: Matthias Blume
386		Date: 2000/06/19 11:05:00 JST
387		Tag: blume-20000619-chdir-bugfix
388		Description:
389
390		Fixed a bug in new SrcPath module that sometimes led to a bad chDir call.
391
392		----------------------------------------------------------------------
393		Name: Matthias Blume
394		Date: 2000/06/18 22:00:10 JST
395		Tag: blume-20000618-implicit-anchors-really-gone
396		Description:
397
398		I updates the previous HISTORY entry where I forgot to mention that
399		implicit anchors are no longer with us.
400
401		The current update also gets rid of the (now useless) controller
402		CM.Control.implicit_anchors.
403
404		----------------------------------------------------------------------
405		Name: Matthias Blume
406		Date: 2000/06/16 17:30:00 JST
407		Tag: blume-20000616-anchorenv
408		Description:
409
410		This patch implements the long anticipated (just kidding :) "anchor
411		environment" mechanism.  In the course of doing this, I also
412		re-implemented CM's internal "SrcPath" module from scratch.  The new
413		one should be more robust in certain boundary cases.  In any case, it
414		is a lot cleaner than its predecessor (IMHO).
415
416		This time, although there is yet another boot file format change, I
417		kept the unpickler backward-compatible.  As a result, no new bootfiles
418		are necessary and bootstrapping is straightforward.  (You cannot read
419		new bootfiles into an old system, but the other way around is no
420		problem.)
421
422		Visible changes:
423
424		** 0. Implicit path anchors (without the leading $-symbol) are no
425		longer recognized at all. This means that such path names are not
426		illegal either.  For example, the name basis.cm simply refers to a
427		local file called "basis.cm" (i.e, the name is an ordinary path
428		relative to .cm-files directory).  Or, to put it differently, only
429		names that start with $ are anchored paths.
430
431		** 1. The $<singlearc> abbreviation for $/<singlearc> has finally
432		vanished.
433
434		John (Reppy) had critizised this as soon as I originally proposed and
435		implemented it, but at that time I did not really deeply believe
436		him. :) Now I came full-circle because I need the $<singlearc> syntax
437		in another place where it cannot be seen as an abbreviation for
438		$/<singlearc>.  To avoid the confusion, $<singlearc> now means what it
439		seems to mean (i.e., it "expands" into the corresponding anchor
440		value).
441
442		However, when paths are used as members in CM description files, it
443		continues to be true that there must be at least another arc after the
444		anchor.  This is now enforced separately during semantic analysis
445		(i.e., from a lexical/syntactical point of view, the notation is ok.)
446
447		** 2. The "cm" class now accepts an option "bind".  The option's value
448		is a sub-option list of precisely two items -- one labeled "anchor"
449		and the other one labeled "value".  As you might expect, "anchor" is
450		used to specify an anchor name to be bound, and "value" specifies what
451		the anchor is being bound to.
452
453		The value must be a directory name and can be given in either standard
454		syntax (including the possibility that it is itself an anchored path)
455		or native syntax.
456
457		Examples:
458
459		foo.cm (bind:(anchor:bar value:$mystuff/bar))
460		lib.cm (bind:(anchor:a value:"H:\\x\\y\\z"))  (* only works under windows *)
461
462		and so on.
463
464		The meaning of this is that the .cm-file will be processed with an
465		augmented anchor environment where the given anchor(s) is/are bound to
466		the given values(s).
467
468		The rationale for having this feature is this: Suppose you are trying
469		to use two different (already stable) libraries a.cm and b.cm (that
470		you perhaps didn't write yourself).  Further, suppose each of these
471		two libraries internally uses its own auxiliary library $aux/lib.cm.
472		Normally you would now have a problem because the anchor "lib" can not
473		be bound to more than one value globally.  Therefore, the project that
474		uses both a.cm and b.cm must locally redirect the anchor to some other
475		place:
476
477		a.cm (bind:(anchor:lib value:/usr/lib/smlnj/a-stuff))
478		b.cm (bind:(anchor:lib value:/usr/lib/smlnj/b-stuff))
479
480		This hard-wires $lib/aux.cm to /usr/lib/smlnj/a-stuff/aux.cm or
481		/usr/lib/smlnj/b-stuff/aux.cm, respectively.
482
483		Hard-wiring path names is a bit inflexible (and CM will verbosely warn
484		you when you do so at the time of CM.stabilize).  Therefore, you can
485		also use an anchored path as the value:
486
487		a.cm (bind:(anchor:lib value:$a-lib))
488		b.cm (bind:(anchor:lib value:$b-lib))
489
490		Now you can globally configure (using the usual CM.Anchor.anchor or
491		pathconfig machinery) bindings for "a-lib" and "b-lib".  Since "lib"
492		itself is always locally bound, setting it globally is no longer
493		meaningful or necessary (but it does not hurt either).  In fact, "lib"
494		can still be used as a global anchor for separate purposes.  As a
495		matter of fact, one can locally define "lib" in terms of a global
496		"lib":
497
498		a.cm (bind:(anchor:lib value:$lib/a))
499		b.cm (bind:(anchor:lib value:$lib/b))
500
501		** 3: The encoding of path names has changed.  This affects the way
502		path names are shown in CM's progress report and also the internal
503		protocol encoding used for parallel make.
504
505		The encoding now uses one or more ':'-separated segments.  Each
506		segments corresponds to a file that has been specified relative to the
507		file given by its preceding segment.  The first segment is either
508		relative to the CWD, absolute, or anchored.  Each segment itself is
509		basically a Unix pathname; all segments but the first are relative.
510
511		Example:
512
513		$foo/bar/baz.cm:a/b/c.sml
514
515		This path denotes the file bar/a/b/c.sml relative to the directory
516		denoted by anchor "foo".  Notice that the encoding also includes
517		baz.cm which is the .cm-file that listed a/b/c.sml.  As usual, such
518		paths are resolved relative to the .cm-files directory, so baz.cm must
519		be ignored to get the "real" pathname.
520
521		To make this fact more obvious, CM puts the names of such "virtual
522		arcs" into parentheses when they appear in progress reports. (No
523		parentheses will appear in the internal protocol encoding.)  Thus,
524		what you really see is:
525
526		$foo/bar/(baz.cm):a/b/c.sml
527
528		I find this notation to be much more informative than before.
529
530		Another new feature of the encoding is that special characters
531		including parentheses, colons, (back)slashes, and white space are
532		written as \ddd (where ddd is the decimal encoding of the character).
533
534		*** The CM manual still needs to be updated.
535
536		----------------------------------------------------------------------
537		Name: Allen Leung
538		Date: 2000/06/15 00:38:00
539		Tag: leunga-20000615-x86-peephole
540
541		x86 Peephole fix by Fermin.  Affects c-- and moby only.
542
543		----------------------------------------------------------------------
544		Name: Matthias Blume
545		Date: 2000/06/12 11:40:00
546		Tag: blume-20000612-parmakefix
547		Description:
548
549		More cleanup after changing the file naming scheme: This time I
550		repaired the parallel make mechanism for CMB.make which I broke earlier.
551
552		----------------------------------------------------------------------
553		Name: Allen Leung
554		Date: 2000/06/09 01:25:00
555		Tag: leunga-20000609-various
556
557		None of these things should affect normal SML/NJ operations
558
559		1. Peephole improvements provided by Fermin (c--)
560		2. New annotation DEFUSE for adding extra dependence (moby)
561		3. New X86 LOCK instructions (moby)
562		4. New machine description language for reservation tables (scheduling)
563		5. Fixes to various optimization/analysis modules (branch chaining, dominator
564		trees etc.)
565		6. I've changed the CM files so that they can work with versions
566		110.0.6, 110.25 and 110.28
567
568		----------------------------------------------------------------------
569		Name: Matthias Blume
570		Date: 2000/06/09 12:40:00
571		Tag: blume-20000609-log
572		Description:
573
574		- Removed all(?) remaining RCS Log entries from sources.
575
576		- Fixed bug in ml-yacc and ml-lex sources (use explicit anchors for
577		anchored paths).
578
579		----------------------------------------------------------------------
580		Name: Matthias Blume
581		Date: 2000/06/07 17:00:00 JST
582		Tag: blume-20000607-no-implicit-anchors
583		Description:
584
585		1. This update changes the default setting for
586		CM.Control.implicit_anchors from true to false.  This means that
587		implicit anchors are no longer permitted by default.  I also tried to
588		make sure that nothing else still relies on implicit anchors.
589		(This is the next step on the schedule towards a CM that does not even
590		have the notion of implicit anchors anymore.)
591
592		2. More CM manual updates.
593
594		3. I managed to track down and fix the pickling bug I mentioned last
595		time.  Because of the previously existing workaround, this entails no
596		immediate practical changes.
597
598		----------------------------------------------------------------------
599		Name: Matthias Blume
600		Date: 2000/06/06 11:15:00 JST
601		Tag: blume-20000606-lazierpickle
602		Description:
603
604		!!!! NEW BOOT FILES !!!!
605
606		* The main purpose of this update is to make library pickles lazier in
607		order to reduce the initial space penalty for autoloading a library.
608		As a result, it is now possible to have $smlnj/compiler.cm
609		pre-registered.  This should take care of the many complaints or
610		inquiries about missing structure Compiler.  This required changes to
611		CM's internal data structures and small tweaks to some algorithms.
612
613		As a neat additional effect, it is no longer necessary (for the sake
614		of lean heap image files) to distinguish between a "minimal" CM and a
615		"full" CM.  Now, there is only one CM (i.e., the "full" version:
616		$smlnj/cm.cm aka $smlnj/cm/full.cm), and it is always available at the
617		interactive top level. ($smlnj/cm/minimal.cm is gone.)
618
619		To make the life of compiler-hackers easier, "makeml" now also
620		pre-registers $smlnj/cmb.cm (aka $smlnj/cmb/current.cm).  In other
621		words, after you bootstrap a new sml for the first time, you will not
622		have to autoload $smlnj/cmb.cm again afterwards.  (The first time
623		around you will still have to do it, though.)
624
625		* A second change consists of major updates to the CM manual.  There
626		are now several appendices with summary information and also a full
627		specification of the CM description file syntax.
628
629		* In directory src/system I added the script "allcross".  This script
630		invokes sml and cross-compiles the compiler for all supported
631		architectures.  (Useful when providing a new set of boot files.)
632
633		* There seems to be a latent bug in my "lazy pickles" mechanism.  I
634		added a small tweak to pickle-util.sml to work around this problem,
635		but it is not a proper fix yet.  I will investigate further.  (The
636		effect of the bug was an inflation of library pickle size.)
637
638		* Version number increased to 110.28.1 (to avoid compatibility problems).
639
640		----------------------------------------------------------------------
641		Name: Allen Leung
642		Date: 2000/05/25 17:28 EDT
643		Tag: leunga-20000525-ra
644		Description:
645
646		Fixed a bug in freezing phase of the register allocator.
647
648		----------------------------------------------------------------------
649		Name: Allen Leung
650		Date: 2000/05/15 22:53 EDT
651		Tag: leunga-20000515-alpha-x86-ra
652		Description:
653
654		1. Alpha
655
656		Slight cleanup.  Removed the instruction SGNXL
657
658		2. X86
659
660		Added the following instructions to the instruction set:
661
662		ROLx, RORx,
663		BTx, BTSx, BTLx, BTRx,
664		XCHGx, and variants with the LOCK prefix
665
666		3. Register Allocation
667
668		The module ra-rewrite-with-renaming has been improved.
669
670		These have no effect on SML/NJ.
671
672		----------------------------------------------------------------------
673		Name: Matthias Blume
674		Date: 2000/05/15 16:20:00 JST
675		Tag: blume-20000515-lightrebuild
676		Description:
677
678		1. I added an alternative to "-rebuild" to "makeml".  The difference is
679		that prior to calling CMB.make' the CM-variable "LIGHT" will be
680		defined.  In effect, the command will not build any cross-compiler
681		backends and therefore finish more quickly.
682
683		The "fixpt" script also takes a "-light" switch to be able to use
684		this new facility while compiling for a fixpoint.
685
686		2. I replaced all mentions of anchored paths in group owner specifications
687		with simple relative paths (usually starting with "..").
688		The rationale is that a library's internal workings should not be
689		compromised by the lack of some anchor.  (An anchor is necessary
690		for someone who wants to refer to the library by an anchored path,
691		but it should not be necessary to build the same library in the first
692		place.)
693
694		3. I changed the way CM's tool mechanism determines the shell command
695		string used for things like ml-yacc etc. so that it does not break
696		when CM.Control.implicit_anchors is turned off.
697
698		----------------------------------------------------------------------
699		Name: Matthias Blume
700		Date: 2000/05/12 18:20:00 JST
701		Tag: blume-20000512-ml-build
702		Description:
703
704		Fixed a bug in config/_ml-build that prevented ml-yacc and ml-lex from
705		getting installed properly (by config/install.sh).
706
707		----------------------------------------------------------------------
708		Name: Matthias Blume
709		Date: 2000/05/12 17:30:00 JST
710		Tag: blume-20000512-anchors
711		Description:
712
713		!!! NEW BOOT FILES !!!
714
715		This change is in preparation of fading out support for "implicitly
716		anchored path names".  I went through all sources and used the
717		explicit (and relatively new) $-notation.  See system/README and the
718		CM manual for more info on this.
719
720		I also modified the anchoring scheme for some things such as "smlnj",
721		"MLRISC", "cm", etc. to take advantage of the fact that explicit
722		anchors are more expressive: anchor name and first arc do not have to
723		coincide.  This entails the following user-visible change:
724
725		You have to write $smlnj/foo/bar instead of smlnj/foo/bar.  In
726		particular, when you fire up sml with a command-line argument, say,
727		e.g.:
728
729		sml '$smlnj/cmb.cm'
730
731		At the ML toplevel prompt:
732
733		CM.autoload "$smlnj/cmb.cm";
734
735		There is also a new controller in CM.Control that can be used to turn
736		off all remaining support for implicit anchors by saying:
737
738		CM.autoload "$smlnj/
739		#set CM.Control.implicit_anchors false;
740
741		This causes CM to reject implicitly anchored paths.  This is (for the
742		time being) less permissive than the "final" version where there will
743		be no more such implicit anchors and relative paths will be just that:
744		relative.
745
746		The next step (version after next version?) will be to make the
747		default for CM.Control.implicit_anchors false.  After the dust has
748		settled, I can then produce the "final" version of this...
749
750		Note: Since bootstrapping is a bit tricky, I provided new boot files.
751
752		----------------------------------------------------------------------
753		Name: Matthias Blume
754		Date: 2000/05/11 16:30:00 JST
755		Tag: blume-20000511-sources
756		Description:
757
758		The main change is that I added function CM.sources as a generalized
759		version of the earlier CM.makedepend.  This entails the following
760		additional changes:
761
762		- CM.makedepend has been dropped.
763
764		- CM manual has been updated.
765
766		- TOOLS signature and API have been changed.
767
768		----------------------------------------------------------------------
769		Name: Allen Leung
770		Date: 2000/05/10 21:17 EDT
771		Tag: leunga-20000510-moby-c--ssa
772		Description:
773
774		Various bug fixes and new features for C--, Moby and MLRISC optimizations.
775		None of these affect SML/NJ.
776
777		1. Register Allocation
778
779		a. A new ra spilling module (ra/ra-spill-with-renaming) is implemented.
780		This module tries to remove local (i.e. basic block level) redundancies
781		during spilling.
782
783		b. A new framework for performing region based register allocation.
784		Not yet entirely functional.
785
786		2. X86
787
788		a. DefUse for POP was missing the stack pointer [found by Lal]
789		b. Reload for CALL was incorrect in X86Spill [found by John]
790		c. Various fixes in X86Spill so that it can be used correctly for
791		the new spilling module.
792
793		3. SSA/IR
794
795		a. New module ir/dj-dataflow.sml implements elimination based
796		data flow analysis.
797
798		4. MLRiscGen
799
800		a. Fix for gc type annotation
801
802		5. MDGen
803
804		Various fixes for machine description -> ml code translation.  For ssa
805		only.
806
807		----------------------------------------------------------------------
808		Name: Allen Leung
809		Date: 2000/05/08 22:17 EDT
810		Tag: leunga-20000508-labexp
811		Description:
812
813		Fermin has found a few assembly problems with constant expressions
814		generated in LabelExp.  Mostly, the problems involve extra parentheses,
815		which choke on dumb assemblers.  This is his fix.
816
817		----------------------------------------------------------------------
818		Name: Dave MacQueen
819		Date: 2000/04/09 14:00 EDT
820		Tag: dbm-20000502-Version_110_28
821		Description:
822
823		1. Updated src/compiler/TopLevel/main/version.sml to version 110.28
824
825		2. Updated config/version to 110.28
826
827		3. Updated config/srcarchiveurl
828
829		3. New boot files!
830		ftp://ftp.research.bell-labs.com/dist/smlnj/working/110.28/
831
832		----------------------------------------------------------------------
833		Name: Matthias Blume
834		Date: 2000/05/01 19:05:00 JST
835		Tag: blume-20000501-noweb
836		Description:
837
838		A new noweb tool has been added.  The existing system is entirely
839		unaffected by this, but some CM users have asked for renewed noweb
840		support.  Everything is documented in the CM manual.
841
842		New (plugin) libraries:
843
844		noweb-tool.cm
845		nw-ext.cm
846
847		----------------------------------------------------------------------
848		Name: Dave MacQueen
849		Date: 2000/04/30 12:40PM EDT
850		Tag: dbm-20000430-bug_fixes
851		Description:
852
853		1. Fix for bug 1498
854		smlnj/src/system/Basis/Implementation/Unsafe/object.sig
855		smlnj/src/system/Basis/Implementation/Unsafe/object.sml
856		added toRealArray function
857		smlnj/src/compiler/MiscUtil/print/ppobj.sml
858		added check for tag Obj.RealArray to array printing case in ppObj
859
860		2. Fix for bug 1510
861		smlnj/src/compiler/Semant/types/typesutil.sml
862		fixed definition of dummyargs (used by equalTycon) so that
863		dummy args are distinct types
864
865		----------------------------------------------------------------------
866		Name: Matthias Blume
867		Date: 2000/04/30 01:00:00 JST
868		Tag: blume-20000430-versions
869		Description:
870
871		1. CM version numbering added.  This is an implementation of Lal's
872		proposal for adding version numbers and version checking to .cm
873		files.  Lal said that his proposal was just that -- a proposal.
874		For the time being I went ahead and implemented it so that people
875		can comment on it.  Everything is completely backward-compatible
876		(except for the stable library format, i.e., new bootfiles!).
877
878		As usual, see the CM manual for details.
879
880		2. An alternative syntax for anchored paths has been implemented.
881		Dave has recently voiced the same concerns that I had when I did
882		this, so there should be some support.  My take is that eventually
883		I will let support for the current syntax (where anchors are
884		"implicit") fade out in favor of the new, explicit syntax.
885		In order to be backward-compatible, both old and new syntax are
886		currently supported.
887
888		Again, see the CM manual for details.
889
890		3. Parallel make is trying to be slightly smarter:  When the master
891		process finds a "bottleneck", i.e., when there is only one
892		compilation unit that can be compiled and everybody else is
893		waiting on it, then it will simply compile it directly instead
894		of clumsily telling one of the slaves to do it.
895
896		4. Support for "unsharing" added.  This is necessary in order to be
897		able to have two different versions of the same library running
898		at the same time (e.g., for trying out a new MLRISC while still
899		having the old MLRISC linked into the current compiler, etc.)
900		See the CM manual.
901
902		5. Simple "makedepend" functionality added for generating Makefile
903		dependency information.  (This is rather crude at the moment.
904		Expect some changes here in the future.)
905
906		6. ".fun" added as a recognized suffix for ML files. Also documented
907		explicitly in the manual that the fallback behavior (unknown suffix
908		-> ML file) is not an official feature!
909
910		7. Small changes to the pickler for stable libraries.
911
912		8. Several internal changes to CM (for cleanup/improvement).
913
914
915		!!!! NEW BINFILES !!!!
916
917		----------------------------------------------------------------------
918		Name: Matthias Blume
919		Date: 2000/04/28 17:30:00 JST
920		Tag: blume-20000428-pathconfig
921		Description:
922
923		1. I changed config/install.sh to remove duplicate entries from the
924		lib/pathconfig file at the end.  Moreover, the final version of
925		lib/pathconfig is sorted alphabetically.  The same (sorting) is done
926		in src/system/installml.
927
928		2. The config/install.sh script now consistently uses relative
929		pathnames in lib/pathconfig whenever the anchor is in the lib
930		directory.  (So far this was true for the libraries that come
931		pre-compiled and bundled as part of the bootfiles but not for
932		libraries that are compiled by the script itself.)
933
934		----------------------------------------------------------------------
935		Name: Matthias Blume
936		Date: 2000/04/26 13:10:00 JST
937		Tag: blume-20000426-fun_suffix
938		Description:
939
940		Added ".fun" as a recognized file name suffix (for ML code).
941
942		----------------------------------------------------------------------
943		Name: Allen Leung
944		Date: 2000/04/25 17:00:00 EST
945		Tag: leunga-20000425-alpha-ra
946		Description:
947
948		1. Alpha
949
950		PSEUDOARITH was missing in AlphaRewrite.  This causes an endless loop
951		in C--.
952
953		2. RA
954
955		Added a flag "ra-dump-size" to print out the size of the flowgraph
956		and the interference graph.
957
958		----------------------------------------------------------------------
959		Name: Dave MacQueen
960		Date: 2000/04/25/
961		Tag: dbm-20000425-mlyacc_doc_examples
962		Description:
963		Updated mlyacc.tex sections 5 and 7 for SML '97 and CM.
964		Updated all three examples in src/ml-yacc/examples to run
965		under 110.* using CM.make.
966
967		----------------------------------------------------------------------
968		Name: Allen Leung
969		Date: 2000/04/20 23:04:00 EST
970		Tag: leunga-20000420-ssa-c---stuff
971		Description:
972
973		This update synchronizes my repository with Yale's.  Most of these
974		changes, however, do not affect SML/NJ at all (the RA is an exception).
975
976		1. Register Allocator
977
978		a. An improvement in the interference graph construction:
979		Given a copy
980
981		s <- t
982
983		no interference edge between s and t is added for this definition of s.
984
985		b. I've added two new spill heuristic modules that Fermin and I developed
986		(in the new library RA.cm). These are unused in SML/NJ but maybe
987		useful for others (Moby?)
988
989		2. X86
990
991		a. Various fixes in the backend provided by Fermin [C--] and Lal.
992
993		3. Alpha
994
995		a. Added the BSR instruction and code generation that goes with it [C--]
996		b. Other fixes too numerous to recount provided by Fermin [C--]
997
998		4. Regmaps
999
1000		a. The regmaps are not initialized with the identity physical bindings
1001		at creation time.  This is unneeded.
1002
1003		5. MLRISC Optimizations
1004
1005		a. The DJ-Graph module can now compute the iterated dominance frontiers
1006		intersects with liveness incrementally in linear time! Woohoo!
1007		This is now used in my new SSA construction algorithm.
1008
1009		b. THe branch reorganization module is now smarter about linear chains of
1010		basic blocks.
1011
1012
1013		----------------------------------------------------------------------
1014		Name: Matthias Blume
1015		Date: 2000/04/12 13:52:00 JST
1016		Tag: blume_main_v110p27_1
1017		Description:
1018
1019		Changed install.sh script to handle archive files without version number
1020		and to use "boot.<arch>-<os>" instead of "sml.boot.<arch>-<os>" for the
1021		name of the boot file archive.
1022
1023		----------------------------------------------------------------------
1024	Name: Dave MacQueen	Name: Dave MacQueen
1025	Date: 2000/04/09 14:00 EDT	Date: 2000/04/09 14:00 EDT
1026	Tag: dbm-20000410-Version_110_27	Tag: dbm-20000410-Version_110_27
#	Line 119	Line 1128
1128
1129	3.  Assembly	3.  Assembly
1130
1131	When generating assemby, resolve the value of client defined constants,	When generating assembly, resolve the value of client defined constants,
1132	instead of generating symbolic values.  This is controlled by the	instead of generating symbolic values.  This is controlled by the
1133	new flag "asm-resolve-constants", which is default to true.	new flag "asm-resolve-constants", which is default to true.
1134
#	Line 142	Line 1151
1151
1152	To this end, I arranged that instead of "structure Core" as "structure	To this end, I arranged that instead of "structure Core" as "structure
1153	_Core" is bound in the pervasive environment.  Core access is done via	_Core" is bound in the pervasive environment.  Core access is done via
1154	_Core (which can never be accidentially rebound because _Core is not a	_Core (which can never be accidentally rebound because _Core is not a
1155	legal surface-syntax symbol).	legal surface-syntax symbol).
1156
1157	The current solution is much cleaner because the core environment is	The current solution is much cleaner because the core environment is
#	Line 152	Line 1161
1161	with dynamic and symbolic parts of the core environment.	with dynamic and symbolic parts of the core environment.
1162
1163	Remaining hackery (to bind the "magic" symbol _Core) is localized in the	Remaining hackery (to bind the "magic" symbol _Core) is localized in the
1164	compilation mananger's bootstrap compiler (actually: in the "init group"	compilation manager's bootstrap compiler (actually: in the "init group"
1165	handling).  See the comments in src/system/smlnj/init/init.cmi for	handling).  See the comments in src/system/smlnj/init/init.cmi for
1166	more details.	more details.
1167
#	Line 267	Line 1276
1276	(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
1277	used).	used).
1278
1279	This was done to accomodate the new "make" and "shell" tools which	This was done to accommodate the new "make" and "shell" tools which
1280	facilitate fairly seemless hookup to portions of code managed using	facilitate fairly seamless hookup to portions of code managed using
1281	Makefiles or Shell scripts.	Makefiles or Shell scripts.
1282
1283	There are no classes "shared" or "private" anymore.  Instead, the	There are no classes "shared" or "private" anymore.  Instead, the
#	Line 280	Line 1289
1289
1290	All existing tools are described in the CM manual.	All existing tools are described in the CM manual.
1291
1292	- Slightly better error handling.  (CM now surpresses many followup	- Slightly better error handling.  (CM now suppresses many followup
1293	error messages that tended to be more annoying than helpful.)	error messages that tended to be more annoying than helpful.)
1294
1295	2. Major changes to the compiler's static environment data structures.	2. Major changes to the compiler's static environment data structures.
#	Line 414	Line 1423
1423
1424	I've changed andl to testl in the floating point test sequence	I've changed andl to testl in the floating point test sequence
1425	whenever appropriate.  The Intel optimization guide states that	whenever appropriate.  The Intel optimization guide states that
1426	testl is perferable to andl.	testl is preferable to andl.
1427
1428	7. RA (x86 only)	7. RA (x86 only)
1429
#	Line 596	Line 1605
1605
1606	1. Tools.registerStdShellCmdTool (from smlnj/cm/tool.cm) takes an	1. Tools.registerStdShellCmdTool (from smlnj/cm/tool.cm) takes an
1607	additional argument called "template" which is an optional string that	additional argument called "template" which is an optional string that
1608	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
1609	explanation.	explanation.
1610
1611	2. A special-purpose tool can be "regisitered" by simply dropping the	2. A special-purpose tool can be "registered" by simply dropping the
1612	corresponding <...>-tool.cm (and/or <...>-ext.cm) into the same	corresponding <...>-tool.cm (and/or <...>-ext.cm) into the same
1613	directory where the .cm file lives that uses this tool.  (The	directory where the .cm file lives that uses this tool.  (The
1614	behavior/misfeature until now was to look for the tool description	behavior/misfeature until now was to look for the tool description
#	Line 643	Line 1652
1652	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
1653	<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,
1654	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
1655	perhaps got accidentially killed).  In this case, fixpt will quickly	perhaps got accidentally killed).  In this case, fixpt will quickly
1656	move through what exists before continuing where it left off earlier,	move through what exists before continuing where it left off earlier,
1657	and, thus, saves a lot of time.	and, thus, saves a lot of time.
1658
#	Line 693	Line 1702
1702	it from that remote directory.	it from that remote directory.
1703	This should simplify installation further:  For machines that have	This should simplify installation further:  For machines that have
1704	access to the internet, just fetch <version>-config.tgz, unpack it,	access to the internet, just fetch <version>-config.tgz, unpack it,
1705	edit config/targets, and go (run config/install.sh).  The scipt will	edit config/targets, and go (run config/install.sh).  The script will
1706	fetch everything else that it might need all by itself.	fetch everything else that it might need all by itself.
1707
1708	For CVS users, this mechanism is not relevant for source archives, but	For CVS users, this mechanism is not relevant for source archives, but

---

Colored Diff Long Colored Diff Unidiff Context Diff Side by Side

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

---

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