unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Subject: Re: scm_remember_upto_here asm volatile
Date: Mon, 19 May 2003 10:24:46 +1000	[thread overview]
Message-ID: <87he7rwzox.fsf@zip.com.au> (raw)
In-Reply-To: <87znll48wr.fsf@zagadka.ping.de> (Marius Vollmer's message of "17 May 2003 22:26:12 +0200")

Marius Vollmer <mvo@zagadka.de> writes:
>
> But please understand that this is a critical and tricky corner of
> Guile.  Bugs might show up on odd platforms and might be very
> sensitive to the environment that scm_remember_upto_here is used in.

With the bignum code, is it true that the only problem will be if a gc
starts in another thread at the critical moment?

If currently the gmp code just uses malloc I guess it won't run a gc
from within the mpz functions as such.  That wasn't the case in the
old code though, if I read scm_i_mkbig rightly.


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


  reply	other threads:[~2003-05-19  0:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-11 22:19 scm_remember_upto_here asm volatile Kevin Ryde
2003-05-17 20:26 ` Marius Vollmer
2003-05-19  0:24   ` Kevin Ryde [this message]
2003-06-01 18:47     ` Marius Vollmer
2003-06-01 19:29       ` Mikael Djurfeldt
2003-08-13 21:09         ` Kevin Ryde
2003-08-23 10:32           ` Dirk Herrmann
2003-08-25 23:48             ` Kevin Ryde
2003-08-27  4:28               ` Dirk Herrmann
2003-08-27 23:49                 ` Kevin Ryde

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=87he7rwzox.fsf@zip.com.au \
    --to=user42@zip.com.au \
    /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).