This is the mail archive of the guile@sourceware.cygnus.com mailing list for the Guile project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: generational GC

To: Michael Livshin <mlivshin at bigfoot dot com>
Subject: Re: generational GC
From: Maciej Stachowiak <mjs at eazel dot com>
Date: 24 Mar 2000 06:01:06 -0800
Cc: clark dot mcgrew at sunysb dot edu, guile at sourceware dot cygnus dot com, Greg dot Harvey at thezone dot net
References: <s3og87v1fm.fsf@verisity.com> <E12XmQD-0001Zo-00@boxer.physics.sunysb.edu> <s3bt47uk6e.fsf@verisity.com> <lqk8itcgys.fsf@pythagoras.eazel.com> <s3r9d0has3.fsf@verisity.com>

Michael Livshin <mlivshin@bigfoot.com> writes:

> Maciej Stachowiak <mjs@eazel.com> writes:
> 
> > Please, no more fundamental system features as compile-time options!
> > Mikael's comments that the app should decide if it wants thread
> > support in Guile, not the sysadmin, is appropriate here too. Although
> > run-time pluggable GC seems like overkill.
> 
> so what are you saying here, then?
> 

I guess the logical conclusion is either provide generational GC only,
or non-generational GC only. This decisions would preferrably be based
on looking at some real-life performance numbers.

 - Maciej

Follow-Ups:
- Re: generational GC
  - From: Mikael Djurfeldt

References:
- generational GC
  - From: Michael Livshin
- Re: generational GC
  - From: Clark McGrew
- Re: generational GC
  - From: Michael Livshin
- Re: generational GC
  - From: Maciej Stachowiak
- Re: generational GC
  - From: Michael Livshin

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]