public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fw at deneb dot enyo.de" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug network/19622] Support aliasing with struct sockaddr Date: Sat, 18 May 2024 11:47:43 +0000 [thread overview] Message-ID: <bug-19622-131-wO20l4SQX8@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-19622-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=19622 Florian Weimer <fw at deneb dot enyo.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED CC| |fw at deneb dot enyo.de Target Milestone|--- |2.40 --- Comment #7 from Florian Weimer <fw at deneb dot enyo.de> --- Fixed for 2.40 via: commit 8d7b6b4cb27d4dec1dd5f7960298c1699275f962 Author: Florian Weimer <fweimer@redhat.com> Date: Sat May 18 09:33:19 2024 +0200 socket: Use may_alias on sockaddr structs (bug 19622) This supports common coding patterns. The GCC C front end before version 7 rejects the may_alias attribute on a struct definition if it was not present in a previous forward declaration, so this attribute can only be conditionally applied. This implements the spirit of the change in Austin Group issue 1641. Suggested-by: Marek Polacek <polacek@redhat.com> Suggested-by: Jakub Jelinek <jakub@redhat.com> Reviewed-by: Sam James <sam@gentoo.org> Reviewed-by: Carlos O'Donell <carlos@redhat.com> -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-05-18 11:47 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-19622-131@http.sourceware.org/bugzilla/> 2024-05-07 9:32 ` fweimer at redhat dot com 2024-05-07 11:39 ` sam at gentoo dot org 2024-05-07 11:40 ` sam at gentoo dot org 2024-05-07 19:42 ` sam at gentoo dot org 2024-05-07 19:54 ` bugdal at aerifal dot cx 2024-05-18 11:47 ` fw at deneb dot enyo.de [this message] 2024-06-13 7:40 ` fweimer at redhat dot com
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-19622-131-wO20l4SQX8@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).