This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/77330] __float128 segfaults on 32-bit x86 due to 8-byte malloc alignment
- From: "joseph at codesourcery dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 23 Aug 2016 22:43:41 +0000
- Subject: [Bug target/77330] __float128 segfaults on 32-bit x86 due to 8-byte malloc alignment
- Auto-submitted: auto-generated
- References: <bug-77330-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77330
--- Comment #10 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Tue, 23 Aug 2016, bernd.edlinger at hotmail dot de wrote:
> Yes, but isn't that an ABI decision?
It's the sort of ABI decision that's fixed after it's appeared in a
release (whereas max_align_t is not the sort of thing that gets embedded
in external ABIs in a way that gets broken when increasing the alignment,
but something you use when writing your own allocator). HJ's i386 ABI
document, version 1.1 is explicit about this ABI choice (and that for
_Decimal128, etc.), so presumably it's intended to be followed the same by
other implementations as well.