unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: Guile + Boehm GC: First Remarks
Date: Fri, 02 Jun 2006 01:01:13 +0100	[thread overview]
Message-ID: <87pshsqvcm.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <e5lf78$min$2@sea.gmane.org> (Han-Wen Nienhuys's message of "Thu, 1 Jun 2006 01:17:29 +0000 (UTC)")

lilydev@muurbloem.xs4all.nl (Han-Wen Nienhuys) writes:

> Boehm is generational, AFAIK.
>
> Virtually everyone uses BGC. GCJ, MzScheme, BigLoog, GNU Obj-C, etc.
>
> See,
>
> http://www.hpl.hp.com/personal/Hans_Boehm/gc/
>
> for a longer list.

Thanks; lots of interesting stuff there.

> By using BGC, you potentially loose a bit of performance, since BGC
> isn't specialized for LISP/Scheme, but you get a system that is much
> better overall researched and tuned.

I like the "better research" and the maintainability angles, but I
don't see how we can say that BGC is "better tuned" than Guile's own
GC, if current data shows it performing less well.

Perhaps we aren't yet running a truly representative set of benchmarks
though?

Regards,
        Neil



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2006-06-02  0:01 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-31  8:49 Guile + Boehm GC: First Remarks Ludovic Courtès
2006-05-31 20:11 ` Neil Jerram
2006-06-01  1:17   ` Han-Wen Nienhuys
2006-06-01  7:22     ` Ludovic Courtès
2006-06-01  7:35       ` Mikael Djurfeldt
2006-06-01  8:28         ` Ludovic Courtès
2006-06-01  8:50           ` Mikael Djurfeldt
2006-06-01  9:42             ` Ludovic Courtès
2006-06-01 12:04               ` Ludovic Courtès
2006-06-04 22:24         ` Han-Wen Nienhuys
2006-06-02  0:01     ` Neil Jerram [this message]
2006-06-02  8:06       ` Mikael Djurfeldt
2006-06-01  7:55   ` Ludovic Courtès
2006-06-02  0:07     ` Neil Jerram
2006-06-02 12:41       ` Ludovic Courtès
2006-10-15  0:04         ` Han-Wen Nienhuys
2006-10-16  7:46           ` Ludovic Courtès
2006-10-18 11:21             ` Han-Wen Nienhuys
2006-10-19 14:25               ` Ludovic Courtès
2006-10-25 18:47                 ` Neil Jerram
2006-10-18 11:34             ` Han-Wen Nienhuys
2006-10-19 14:28               ` Ludovic Courtès
2006-10-18 14:42             ` Han-Wen Nienhuys
2006-11-26 18:48               ` Ludovic Courtès
2006-10-18 14:59             ` Han-Wen Nienhuys
2006-10-18 15:42             ` Han-Wen Nienhuys
2006-10-18 16:10             ` Han-Wen Nienhuys
2006-10-18 16:53             ` Han-Wen Nienhuys
2006-06-01  1:10 ` Han-Wen Nienhuys
2006-06-01  8:09   ` Ludovic Courtès
2006-06-18 18:00 ` Clinton Ebadi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pshsqvcm.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).