Commit 6a837e64cf70651bfa16e0d6090ffb4122a2f76f | zig

author	Matthew Lugg <mlugg@mlugg.co.uk> 2025-01-10 05:35:03+00:00
committer	Matthew Lugg <mlugg@mlugg.co.uk> 2025-01-10 05:41:21+00:00
log	6a837e64cf70651bfa16e0d6090ffb4122a2f76f
tree	1d344d3bdeb485e43903a4b42e82f92e1836d395
parent	e9bd2d45d4bbaf7eff7e95bc3ef7a0123b66a103
signature	Commit is signed but in an unrecognized format.

compiler: bump stack size 32 MiB -> 46 MiB

Before the prior commit, the maximum comptime recursion depth on my
system was 4062. After the prior commit, it decreased to 2854. This
commit increases the compiler's stack size enough so that the recursion
depth limit is no less than it was before the `Sema.analyzeCall`
rewrite, preventing this from being a breaking change. Specifically,
this stack size increases my observed maximum comptime recursion depth
to 4105.

1 files changed, 1 insertions(+), 1 deletions(-)

build.zig

build.zig+1-1

...	@@ -11,7 +11,7 @@ const assert = std.debug.assert;	...	@@ -11,7 +11,7 @@ const assert = std.debug.assert;
11	const DevEnv = @import("src/dev.zig").Env;	11	const DevEnv = @import("src/dev.zig").Env;
12		12
13	const zig_version: std.SemanticVersion = .{ .major = 0, .minor = 14, .patch = 0 };	13	const zig_version: std.SemanticVersion = .{ .major = 0, .minor = 14, .patch = 0 };
14	const stack_size = 32 * 1024 * 1024;	14	const stack_size = 46 * 1024 * 1024;
15		15
16	pub fn build(b: *std.Build) !void {	16	pub fn build(b: *std.Build) !void {
17	const only_c = b.option(bool, "only-c", "Translate the Zig compiler to C code, with only the C backend enabled") orelse false;	17	const only_c = b.option(bool, "only-c", "Translate the Zig compiler to C code, with only the C backend enabled") orelse false;