https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25914
--- Comment #8 from Eric Gallager ---
(In reply to dave.anglin from comment #7)
> On 2018-05-07 4:05 PM, egallager at gcc dot gnu.org wrote:
> > Did this proposal ever happen?
> Yes:
> http://pubs.opengroup.org/onlinepubs/9699919799/functions/psi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25914
--- Comment #7 from dave.anglin at bell dot net ---
On 2018-05-07 4:05 PM, egallager at gcc dot gnu.org wrote:
> Did this proposal ever happen?
Yes:
http://pubs.opengroup.org/onlinepubs/9699919799/functions/psignal.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25914
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
--- Comment
--- Comment #5 from danglin at gcc dot gnu dot org 2006-02-22 15:22 ---
The libiberty version is documented as unsigned and has been this
way for many years. The Open Group has a strawman proposal which may
be submitted to the Austin Group for addition to POSIX in its next
release. It
--- Comment #4 from dave at hiauly1 dot hia dot nrc dot ca 2006-01-27
00:12 ---
Subject: Re: strsignal.c:558: warning: comparison between signed and unsigned
> It is unsigned int on Solaris too. Seems like glibc/Linux is the out man out
> really as this was developed by the BSD folks
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-01-26 23:09 ---
It is unsigned int on Solaris too. Seems like glibc/Linux is the out man out
really as this was developed by the BSD folks.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25914
--- Comment #2 from sje at cup dot hp dot com 2006-01-26 21:56 ---
It looks like linux (including LSB 3.1 standard) uses an int argument in
psignal
and Apple/BSD systems use an unsigned int argument. I don't see psignal in any
ANSI or POSIX standards.
The libiberty version is currently
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-01-23 14:51 ---
Confirmed.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCON
