This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug go/67198] [5/6 Regression] change of type of syscall.RawSockaddr.Data on ppc64 breaks compilation of existing programs
- From: "ian at airs dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 13 Aug 2015 15:46:36 +0000
- Subject: [Bug go/67198] [5/6 Regression] change of type of syscall.RawSockaddr.Data on ppc64 breaks compilation of existing programs
- Auto-submitted: auto-generated
- References: <bug-67198-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67198
--- Comment #5 from Ian Lance Taylor <ian at airs dot com> ---
I am indeed saying that no code is ever going to do a less-than or greater-than
comparison with the bytes in an IP address.
Not that that has much to do with what we should do here. I'm just saying that
the possibility of code that behaves incorrectly because these bytes are signed
or unsigned is not an issue. It won't happen and we should not worry about it.
What matters is whether programs compile or not.