Re: Storage management, was Compile-time garbage collection (was Re: Compiler writers will love this language)

> > > I admit, reference-counting has its problems and I have been toying
> > > around with an idea for what I call "compile-time
> > > reference-counting". ...
> >
> > Be sure to look up existing work. I'm certain that people have worked
> > on this kind of thing.
>
> I've been looking around for something similar, the most I've found is
> this paper:
>
> Ran Shaham, Eran Yahav, Elliot K. Kolodner, and Mooly Sagiv,
> Establishing Local Temporal Heap Safety Properties with Applications to
> Compile-Time Memory Management. To appear in the 10th Annual
> International Static Analysis Symposium (SAS '03) San Diego, California,
> USA, June 2003.
>
> Available from the author's web page at
> http://www.math.tau.ac.il/~ransh/ (direct:
> http://www.math.tau.ac.il/~rans/sas03-safety-mm.pdf )


Well, here are some more:


Simon B. Jones and M. White. Is compile time garbage collection worth the
effort. In Peyton Jones et al. Simon L. Peyton Jones, G. Hutton, and C. K.
Hols, editors. Third Annual Glasgow Workshop on Functional Programming.
Springer-Verlag, 1991, pages 172-176
Couldn't find this one


Simon B. Jones and Andrew S. Tyas. The implementer's dilemma: A mathematical
model of compile-time garbage collection. In Sixth Annual Glasgow Workshop
on Functional Programming, Workshops in Computer Science. Springer-Verlag,
1993, pages 139-144
file://ftp.cs.stir.ac.uk/pub/tr/cs/1994/TR118.ps.Z


Simon B. Jones. An experiment in compile time garbage collection. Technical
Report 84, Programming Methodology Group, Göteborg University and Chalmers
University of Technology, January 1995
file://ftp.cs.stir.ac.uk/pub/tr/cs/1994/TR127.ps.Z


Thomas P. Jensen and Torben Mogensen. A backwards analysis for compile-time
garbage collection. In Neil D. Jones, editor, ESOP'90 3rd European Symposium
on Programming, Copenhagen, Denmark, May 1990. (Lecture Notes in Computer
Science, vol. 432), pages 227-239. Springer-Verlag, 1990
Couldn't find this one online


Compile-time garbage collection by sharing analysis. In ACM Func. Prog.
Langs. and Comp. Arch. (FPCA), 1989, pages 54-74. (not complete)
Available from acm.org
So far none of them account for threads -- you can augment them to support
global variables by annotating each function with the global variables that
it (and its callees) uses and modifies and treating those as part of the
parameters/returns of the function.

Return to the comp.compilers page.
Search the comp.compilers archives again.