commit 98b60992b334df16db1c7f99be466d252d61c4bc (tree)
parent e50789f1cb13522a3bdace2a2359711163c3fd55
Author: Cody Tapscott <topolarity@tapscott.me>
Date: Tue, 1 Nov 2022 06:20:28 -0700
stage2: Ensure f128 alignment matches c_longdouble alignment
On platforms where c_longdouble is 128-bits, interop with C code
is simplified by making f128 match the alignment of c_longdouble.
I intended to make this change as part of #13257, but I missed this
part.
Diffstat:
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/src/type.zig b/src/type.zig
@@ -2919,7 +2919,10 @@ pub const Type = extern union {
return AbiAlignmentAdvanced{ .scalar = abiAlignment(u80_ty, target) };
},
},
- .f128 => return AbiAlignmentAdvanced{ .scalar = 16 },
+ .f128 => switch (CType.longdouble.sizeInBits(target)) {
+ 128 => return AbiAlignmentAdvanced{ .scalar = CType.longdouble.alignment(target) },
+ else => return AbiAlignmentAdvanced{ .scalar = 16 },
+ },
// TODO revisit this when we have the concept of the error tag type
.anyerror_void_error_union,