unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.homelinux.net>
To: Rob Browning <rlb@defaultvalue.org>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel@gnu.org
Subject: Re: Thread+GC issues on ARM
Date: Mon, 13 Feb 2012 22:22:07 +0000	[thread overview]
Message-ID: <87vcnajrw0.fsf@neil-laptop.ossau.uklinux.net> (raw)
In-Reply-To: <87hayxcls0.fsf@trouble.defaultvalue.org> (Rob Browning's message of "Sat, 11 Feb 2012 11:39:11 -0600")

Rob Browning <rlb@defaultvalue.org> writes:

> Though if it wasn't too difficult to come up with a reasonable patch,
> we could ask the Debian libgc maintainer to apply it to the older
> version.

I don't yet know if there is such a patch.  I can imagine a procedure
for trying to find it: first git bisect to find the oldest libgc source
for which Guile builds and passes make check, then, either automatically
or by hand, try to identify the precise commits, up to that point, that
are what Guile needs...  But I think this would be difficult and
time-consuming.  Let's wait for a while first to see if the 7.2 release
materialises!

       Neil



  reply	other threads:[~2012-02-13 22:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-24 12:50 Thread+GC issues on ARM Neil Jerram
2012-01-07  1:39 ` Andy Wingo
2012-01-07  3:32   ` Rob Browning
2012-01-07 12:01     ` Neil Jerram
2012-01-07 12:35       ` Neil Jerram
2012-01-07 17:52         ` Rob Browning
2012-01-08 10:28           ` Neil Jerram
2012-02-11  3:39             ` Rob Browning
2012-02-11  9:58               ` Neil Jerram
2012-02-11 13:10                 ` Neil Jerram
2012-02-11 17:39                   ` Rob Browning
2012-02-13 22:22                     ` Neil Jerram [this message]
2012-02-11 17:38                 ` Rob Browning
2013-01-16 10:28               ` Andy Wingo
2012-01-07 16:48       ` Rob Browning

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=87vcnajrw0.fsf@neil-laptop.ossau.uklinux.net \
    --to=neil@ossau.homelinux.net \
    --cc=guile-devel@gnu.org \
    --cc=rlb@defaultvalue.org \
    --cc=wingo@pobox.com \
    /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).