this doesn't contradict OpenBSD's man page, and I'm not sure what you find funny in it. It says -fstrict-aliasing causes issues…
musl's getaddrinfo looks clean/correct here: https://git.musl-libc.org/cgit/musl/tree/src/network/getaddrinfo.c?h=v1.1.15#n64 …
-
-
musl's getnameinfo probably has one minor sockaddr aliasing error: https://git.musl-libc.org/cgit/musl/tree/src/network/getnameinfo.c?h=v1.1.15#n131 …
-
res_msend may have a tiny issue if bind() were 3rd-party, but since it's ours and just a syscall, it's ok: https://git.musl-libc.org/cgit/musl/tree/src/network/res_msend.c?h=v1.1.15#n71 …
-
And finally getifaddrs may have some sockaddr aliasing issues; I'm not familiar enough with that code to judge immediately.
-
Everything else in musl looks clean with respect to struct sockaddr.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.