From: Werner Scheinast <W.Scheinast@web.de>
Cc: bug-guile@gnu.org
Subject: Re: 1.7.2: scmsigs.c,signal_delivery_thread
Date: Mon, 9 May 2005 18:58:30 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0505091747510.1304@kt12.fz-rossendorf.de> (raw)
In-Reply-To: <87vf5viz57.fsf@zip.com.au>
Am 07.05.05 schrieb KevinRyde:
> Werner Scheinast <W.Scheinast@web.de> writes:
> >
> > -Wall
>
> Did you add that? It's probably not a good idea.
No, it was done automatically. (Or can there be a system-wide default
option string?) I only added some processor optimization.
> > scmsigs.c: In function `signal_delivery_thread':
> > scmsigs.c:152: warning: no return statement in function returning non-void
>
> I don't think that function ever returns, gcc probably shouldn't
> complain about such cases.
I wonder why he reports a mere "warning" and then stops with a fatal
error.
> I guess it could be void, but the function pointer is used in a spot
> where the prototype should be an SCM return.
When I say "void", he exits with another message:
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I.. -pthread -O3 -march=pentium4
-mfpmath=sse -msse2 -Wall -Wmissing-prototypes -Werror -MT
libguile_la-scmsigs.lo -MD -MP -MF .deps/libguile_la-scmsigs.Tpo -c
scmsigs.c -fPIC -DPIC -o .libs/libguile_la-scmsigs.o
scmsigs.c:125: error: two or more data types in declaration of
`signal_delivery_thread'
scmsigs.c: In function `start_signal_delivery_thread':
scmsigs.c:160: warning: passing arg 1 of `scm_spawn_thread' from
incompatible pointer type
make[2]: *** [libguile_la-scmsigs.lo] Fehler 1
make[2]: Leaving directory `/home/werner/Archiv/guile-1.7.2/libguile'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/home/werner/Archiv/guile-1.7.2'
make: *** [all] Fehler 2
When I follow Paul's suggestion and add "__attribute__((noreturn))" before
the function name (right?), it doesn't change anything.
Perhaps the mistake is somewhere else ... in my SuSE version of the gcc
compiler or so ...?
Thanks anyway for the tips
Werner
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2005-05-09 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 12:57 1.7.2: scmsigs.c,signal_delivery_thread Werner Scheinast
2005-05-07 1:49 ` Kevin Ryde
2005-05-09 15:29 ` Paul Jarc
2005-05-09 16:58 ` Werner Scheinast [this message]
2005-05-09 19:01 ` Neil Jerram
2005-05-10 12:16 ` Werner Scheinast
2005-05-10 20:06 ` Neil Jerram
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=Pine.LNX.4.58.0505091747510.1304@kt12.fz-rossendorf.de \
--to=w.scheinast@web.de \
--cc=bug-guile@gnu.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).