Date: Thu, 25 Oct 2012 09:11:35 +1100 From: Brett <brett.mahar@gmx.com> To: svn-src-head@freebsd.org Subject: Re: svn commit: r242014 - head/sys/kern Message-ID: <20121025091135.6df6b1d1221fed10c81b9cb5@gmx.com> In-Reply-To: <508855DA.1080903@freebsd.org> References: <201210241836.q9OIafqo073002@svn.freebsd.org> <201210241443.25988.jhb@freebsd.org> <CAJP=Hc9wLv02sX%2BWnzZtaKccSAFzqg8jT0oP13nLw1jMfwOEBQ@mail.gmail.com> <CAJ-FndDzBdq8q6J7QKqf=abi_702s_ia=pa3XbBv80rxbGb-SA@mail.gmail.com> <50884E9F.3090706@freebsd.org> <CAJ-FndBH2cjF2ukt4373BwMsoWEeLykBhPQNnXUgpJ=4jd3LJg@mail.gmail.com> <508855DA.1080903@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> >>> As I've already said in another thread __align() doesn't work on > >>> object declaration, so what that won't pad it either if it is global > >>> or part of a struct. > >>> It is just implemented as __attribute__((aligned(X))): > >>> http://gcc.gnu.org/onlinedocs/gcc-3.2/gcc/Type-Attributes.html > The problem we have is that is apparently doesn't work correctly > within gcc when creating structs nor within the linker when placing > such supposedly aligned structs in the .bss section (at least the > padding is missing). > > It seems to come down to either a) fixing gcc+ld; or b) hacking > around it by magically padding the structs that require it. Isn't -current switching over to Clang pretty soon? In that case, why worry about what gcc does? Brett.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121025091135.6df6b1d1221fed10c81b9cb5>