From: Andy Wingo <wingo@pobox.com>
To: "Boehm\, Hans" <hans.boehm@hp.com>
Cc: bug-guile <bug-guile@gnu.org>,
"gc@linux.hpl.hp.com" <gc@linux.hpl.hp.com>,
Ivan Maidanski <ivmai@mail.ru>
Subject: Re: [Gc] pthreads and libgc
Date: Fri, 25 Mar 2011 15:49:26 +0100 [thread overview]
Message-ID: <m3lj03gsqx.fsf@unquote.localdomain> (raw)
In-Reply-To: <238A96A773B3934685A7269CC8A8D04272EFCB8D2E@GVW0436EXB.americas.hpqcorp.net> (Hans Boehm's message of "Sun, 20 Mar 2011 03:51:05 +0000")
On Sun 20 Mar 2011 04:51, "Boehm, Hans" <hans.boehm@hp.com> writes:
> For newer collectors, it might be possible to instead arrange for
> pthread_create not to be redirected to GC_pthread_create, and for
> threads that need to be known to the GC to register themselves. I
> haven't thought through whether that might be feasible here.
I have done this, and it seems to work, though I have a leak to track
down, yet. I'll let the list know if I get stuck again. But in the
meantime, thanks very much for the help!
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-03-25 14:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 20:56 pthreads and libgc Andy Wingo
[not found] ` <m37hbwxi57.fsf-CaTCM8lwFkgB9AHHLWeGtNQXobZC6xk2@public.gmane.org>
2011-03-19 19:18 ` Ivan Maidanski
2011-03-19 23:26 ` [Gc] " Andy Wingo
[not found] ` <m3zkoqvgis.fsf-CaTCM8lwFkgB9AHHLWeGtNQXobZC6xk2@public.gmane.org>
2011-03-20 3:51 ` Boehm, Hans
2011-03-21 9:29 ` Ludovic Courtès
2011-03-25 14:49 ` Andy Wingo [this message]
2011-04-15 21:35 ` Calling ‘GC_INIT’ from a secondary thread Ludovic Courtès
2011-04-16 9:38 ` [Gc] Calling ‘GC_INIT’from " Ivan Maidanski
2011-04-17 14:01 ` Ludovic Courtès
2011-04-17 14:11 ` Re[2]: [Gc] Calling ‘GC_INIT’ from " Ivan Maidanski
2011-04-17 19:49 ` Ludovic Courtès
2011-04-18 22:18 ` Re[2]: [Gc] Calling ‘GC_INIT’ from a secondarythread Ivan Maidanski
2011-03-20 10:45 ` Re[2]: pthreads and libgc Ivan Maidanski
2011-03-25 14:48 ` [Gc] " Andy Wingo
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=m3lj03gsqx.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=gc@linux.hpl.hp.com \
--cc=hans.boehm@hp.com \
--cc=ivmai@mail.ru \
/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).