public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug network/16421] IN6_IS_ADDR_UNSPECIFIED can use undefined s6_addr32 Date: Tue, 04 Feb 2014 18:16:00 -0000 [thread overview] Message-ID: <bug-16421-131-A48ZkVezo9@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16421-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=16421 --- Comment #15 from Carlos O'Donell <carlos at redhat dot com> --- On 02/04/2014 01:08 PM, alvarezp at alvarezp dot ods.org wrote: >> Not an option. Please leave the __GNUC__ implementation for optimally >> supporting those using GNU extensions. > > Patch #1, the original one from Sebastien does exactly that. Repost that patch to libc-alpha then for review. >> The fix I'll accept is: >> >> - Unconditionally define __u6_* in the union. >> - Fix all the macros. >> - Test that. > > By "fix all the macros", do you mean, rewrite them so they don't use statement > expressions? No, I mean fix them to use __u6_* in the union reference so they operate independently of the public definitions of the struct members. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-02-04 18:16 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-09 12:46 [Bug network/16421] New: " kazssym at vx68k dot org 2014-01-10 19:58 ` [Bug network/16421] " bugdal at aerifal dot cx 2014-01-11 9:57 ` kazssym at vx68k dot org 2014-01-11 15:29 ` bugdal at aerifal dot cx 2014-02-04 4:09 ` carlos at redhat dot com 2014-02-04 4:11 ` carlos at redhat dot com 2014-02-04 4:12 ` carlos at redhat dot com 2014-02-04 4:14 ` alvarezp at alvarezp dot ods.org 2014-02-04 4:59 ` alvarezp at alvarezp dot ods.org 2014-02-04 5:11 ` alvarezp at alvarezp dot ods.org 2014-02-04 14:55 ` carlos at redhat dot com 2014-02-04 17:30 ` alvarezp at alvarezp dot ods.org 2014-02-04 17:46 ` carlos at redhat dot com 2014-02-04 18:08 ` alvarezp at alvarezp dot ods.org 2014-02-04 18:16 ` carlos at redhat dot com [this message] 2014-02-04 18:55 ` carlos at redhat dot com 2014-02-04 18:57 ` carlos at redhat dot com 2014-02-04 22:30 ` alvarezp at alvarezp dot ods.org 2014-02-04 22:38 ` alvarezp at alvarezp dot ods.org 2014-02-04 22:51 ` joseph at codesourcery dot com 2014-02-04 22:54 ` carlos at redhat dot com 2014-02-05 0:03 ` joseph at codesourcery dot com 2014-02-06 23:13 ` alvarezp at alvarezp dot ods.org 2014-02-28 20:47 ` alvarezp at alvarezp dot ods.org 2014-06-13 9:08 ` fweimer at redhat dot com 2015-04-23 13:41 ` alvarezp at alvarezp dot ods.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-16421-131-A48ZkVezo9@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).