This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/20111] struct sockaddr_storage cannot be aggregate-copied
- From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Mon, 23 May 2016 18:11:50 +0000
- Subject: [Bug libc/20111] struct sockaddr_storage cannot be aggregate-copied
- Auto-submitted: auto-generated
- References: <bug-20111-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20111
--- Comment #7 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".
The branch, bug20111 has been created
at 3375cfafa7961c6ae0e509c31c3b3cef9ad1f03d (commit)
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=3375cfafa7961c6ae0e509c31c3b3cef9ad1f03d
commit 3375cfafa7961c6ae0e509c31c3b3cef9ad1f03d
Author: Florian Weimer <fweimer@redhat.com>
Date: Mon May 23 19:43:09 2016 +0200
Make padding in struct sockaddr_storage explicit [BZ #20111]
This avoids aliasing issues with GCC 6 in -fno-strict-aliasing
mode. (With implicit padding, not all data is copied.)
This change makes it explicit that struct sockaddr_storage is
only 126 bytes large on m68k (unlike elsewhere, where we end up
with the requested 128 bytes). The new test case makes sure that
this does not happen on other architectures.
-----------------------------------------------------------------------
--
You are receiving this mail because:
You are on the CC list for the bug.