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, Neil Jerram <neil@ossau.uklinux.net>,
	ldv@altlinux.org
Subject: Re: guile-1.8.1 - problems on AMD64
Date: Mon, 16 Oct 2006 10:04:35 +0200	[thread overview]
Message-ID: <873b9ou1nw.fsf@laas.fr> (raw)
In-Reply-To: <20061016062540.GE17598@basalt.office.altlinux.org> (Stanislav Ievlev's message of "Mon, 16 Oct 2006 10:25:40 +0400")

Hi,

Stanislav Ievlev <inger@altlinux.org> writes:

> On Sat, Oct 14, 2006 at 02:13:38PM +0100, Neil Jerram wrote:
>> ludovic.courtes@laas.fr (Ludovic Court?s) writes:
>> 
>> > As for this:
>> >
>> >   async.c: In function 'scm_i_queue_async_cell':
>> >   async.c:250: warning: ignoring return value of 'write', declared with attribute warn_unused_result
>> >
>> > I don't really understand what this code does, but I have the feeling
>> > that line 250 could be rewritten this way:
>> >
>> >   SCM_SYSCALL ((void)write (sleep_fd, &dummy, 1));
>> >
>> > Can somebody familiar with this comment?
>> 
>> Agreed.  Stanislav, can you try this and confirm whether it removes
>> the warning you are getting?
>
> New compiller is a too smart for it ;)

I guess the point of this `_FORTIFY_SOURCE' thing is to help catch
errors related to interactions with the kernel (among others).  The idea
is that when performing a system call, one _should_ be concerned about
its result.

In the case of async.c:250, I don't understand whether/how failure of
the `write ()' call should be handled.

Thanks,
Ludovic.


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


  reply	other threads:[~2006-10-16  8:04 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 [this message]
2006-10-19 18:46                 ` Neil Jerram
2006-10-21 13:12                   ` Ludovic Courtès

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=873b9ou1nw.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    --cc=guile-devel@gnu.org \
    --cc=ldv@altlinux.org \
    --cc=neil@ossau.uklinux.net \
    /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).