From 480e7eec65c02952b71ecc2f4ff2adccb6092a5f Mon Sep 17 00:00:00 2001 From: Cody Tapscott Date: Tue, 15 Mar 2022 14:00:33 -0700 Subject: stage2: Fix panic on initializing comptime fields in tuple This resolves https://github.com/ziglang/zig/issues/11159 The problem was that: 1. We were not correctly deleting the field stores after recognizing that an array initializer was a comptime-known value. 2. LLVM was not checking that the final type had no runtime bits, and so would generate an invalid store. This also adds several test cases for related bugs, just to check these in for later work. --- test/behavior.zig | 3 +++ 1 file changed, 3 insertions(+) (limited to 'test/behavior.zig') diff --git a/test/behavior.zig b/test/behavior.zig index edc9953e59..f142464dc3 100644 --- a/test/behavior.zig +++ b/test/behavior.zig @@ -65,8 +65,11 @@ test { _ = @import("behavior/bugs/10970.zig"); _ = @import("behavior/bugs/11046.zig"); _ = @import("behavior/bugs/11139.zig"); + _ = @import("behavior/bugs/11159.zig"); + _ = @import("behavior/bugs/11162.zig"); _ = @import("behavior/bugs/11165.zig"); _ = @import("behavior/bugs/11181.zig"); + _ = @import("behavior/bugs/11182.zig"); _ = @import("behavior/call.zig"); _ = @import("behavior/cast.zig"); _ = @import("behavior/comptime_memory.zig"); -- cgit v1.2.3