[Bug other/25914] strsignal.c:558: warning: comparison between signed and unsigned
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/psignal.html OK, so... time to change the libiberty one then? Or is it too late?
[Bug other/25914] strsignal.c:558: warning: comparison between signed and unsigned
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
[Bug other/25914] strsignal.c:558: warning: comparison between signed and unsigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25914 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org --- Comment #6 from Eric Gallager --- (In reply to John David Anglin from comment #5) > 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 uses a signed int. Did this proposal ever happen?
[Bug other/25914] strsignal.c:558: warning: comparison between signed and unsigned
--- 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 uses a signed int. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25914
[Bug other/25914] strsignal.c:558: warning: comparison between signed and unsigned
--- 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. The Linux manpage says: CONFORMING TO 4.3BSD I don't have access to a 4.3BSD system but DEC Ultrix is unsigned, so it looks to me like the Linux folks have messed up. It's unfortunate but the Linux version is what made it to ISO 23360. Dave -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25914
[Bug other/25914] strsignal.c:558: warning: comparison between signed and unsigned
--- 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
[Bug other/25914] strsignal.c:558: warning: comparison between signed and unsigned
--- 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 an unsigned int. -- sje at cup dot hp dot com changed: What|Removed |Added CC||sje at cup dot hp dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25914
[Bug other/25914] strsignal.c:558: warning: comparison between signed and unsigned
--- 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|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2006-01-23 14:51:02 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25914
