From: Clinton Ebadi <clinton@unknownlamer.org>
Cc: Guile-Devel <guile-devel@gnu.org>
Subject: Re: Guile + Boehm GC: First Remarks
Date: Sun, 18 Jun 2006 14:00:10 -0400 [thread overview]
Message-ID: <1150653610.23373.38.camel@localhost.localdomain> (raw)
In-Reply-To: <877j42r32u.fsf@laas.fr>
[-- Attachment #1.1: Type: text/plain, Size: 1302 bytes --]
On Wed, 2006-05-31 at 10:49 +0200, Ludovic Courtès wrote:
> You can get it from my Arch archive:
>
> $ tla register-archive http://www.laas.fr/~lcourtes/software/arch-2005
> $ tla get -A lcourtes@laas.fr--2005-libre guile-core--boehm-gc--1.9 \
> guile-core--bgc
>
> A tarball and a diff against current CVS HEAD are also available:
>
> http://www.laas.fr/~lcourtes/software/arch-2005/guile-core/guile-core--boehm-gc/guile-core--boehm-gc--1.9/patch-35/guile-core--boehm-gc--1.9--patch-35.tar.gz
> http://www.laas.fr/~lcourtes/software/guile/guile-core--bgc--patch-35.diff.gz
>
> SHA1 sums:
>
> 6b6867dc637a24d7f9f25f99fb7d81c8a54b9190 guile-core--bgc--patch-35.diff.gz
> 4a54c2489dbca7e5415be788c3d1fdc9884584f9 guile-core--boehm-gc--1.9--patch-35.tar.gz
>
Your patch touches a lot of files and reverts them to older versions.
Could you resync with cvs head, and send another patch with only the
real changes? If you don't have time I can do it.
Has anyone actually tried testing the performance of a real guile
program with the patch yet?
--
http://unknownlamer.org
Jabber: clinton@hcoop.net AIM:unknownlamer IRC:unknown_lamer@fnode#tpu
Real Men use Free Software; Open Source is for tools
443E 4F1A E213 7C54 A306 E328 7601 A1F0 F403 574B
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2006-06-18 18:00 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
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 [this message]
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=1150653610.23373.38.camel@localhost.localdomain \
--to=clinton@unknownlamer.org \
--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).