unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: guile-devel@gnu.org, ldv@altlinux.org
Subject: Re: guile-1.8.1 - problems on AMD64
Date: Sat, 21 Oct 2006 15:12:32 +0200	[thread overview]
Message-ID: <87iridyfr3.fsf@laas.fr> (raw)
In-Reply-To: <871wp43zzz.fsf@ossau.uklinux.net> (Neil Jerram's message of "Thu, 19 Oct 2006 19:46:24 +0100")

Hi,

Neil Jerram <neil@ossau.uklinux.net> writes:

> I think it's writing a byte as an inter-thread signaling mechanism.
> It's pretty unlikely that a single byte write will be interrupted, but
> if it is then a retry will be needed, so I think the use of
> SCM_SYSCALL is correct in principle here.

Ok.

> How about this, which is more similarly to the other uses of
> SCM_SYSCALL in the code?
>
>       SCM_SYSCALL (rv = write (sleep_fd, &dummy, 1));

Looks good.  How about also checking whether RV is actually equal to 1
then (and loop if it's lower than 1)?

(I know it is unlikely that RV will be different from 1 but the API
specification leaves this possibility open and it's certainly not
impossible.)

Thanks,
Ludovic.


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


      reply	other threads:[~2006-10-21 13:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10  6:34 guile-1.8.1 - problems on AMD64 Stanislav Ievlev
2006-10-10  8:23 ` Ludovic Courtès
2006-10-11 11:01   ` Stanislav Ievlev
2006-10-11 20:08     ` Kevin Ryde
2006-10-12 12:58     ` Ludovic Courtès
2006-10-13  6:26       ` Stanislav Ievlev
2006-10-13  7:38         ` Ludovic Courtès
2006-10-14 13:13           ` Neil Jerram
2006-10-16  6:25             ` Stanislav Ievlev
2006-10-16  8:04               ` Ludovic Courtès
2006-10-19 18:46                 ` Neil Jerram
2006-10-21 13:12                   ` Ludovic Courtès [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=87iridyfr3.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    --cc=guile-devel@gnu.org \
    --cc=ldv@altlinux.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).