[Bug c/61846] gcc assumes errno might be negative and issues unnecessary warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61846 --- Comment #5 from Zbigniew Jędrzejewski-Szmek --- (In reply to Andrew Pinski from comment #4) > C99 also has this requirement. But C89 did not. The warnings are "best effort" anyway. So even if the standards did *not* say that, gcc could skip

[Bug c/61846] gcc assumes errno might be negative and issues unnecessary warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61846 --- Comment #4 from Andrew Pinski --- C99 also has this requirement. But C89 did not. >Values for errno are now required to be distinct positive values rather than > non-zero values. This change is for alignment with the ISO/IEC 9899:1999 > s

[Bug c/61846] gcc assumes errno might be negative and issues unnecessary warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61846 Zbigniew Jędrzejewski-Szmek changed: What|Removed |Added Attachment #33148|0 |1 is obsolete|

[Bug c/61846] gcc assumes errno might be negative and issues unnecessary warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61846 --- Comment #2 from Zbigniew Jędrzejewski-Szmek --- Created attachment 33151 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33151&action=edit processed source

[Bug c/61846] gcc assumes errno might be negative and issues unnecessary warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61846 --- Comment #1 from Zbigniew Jędrzejewski-Szmek --- Created attachment 33150 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33150&action=edit compilation logs