zig/test/link/macho/unwind_info/build.zig

85 lines
2.3 KiB
Zig
Raw Normal View History

const std = @import("std");
const builtin = @import("builtin");
2023-03-08 03:23:11 +00:00
pub const requires_symlinks = true;
pub fn build(b: *std.Build) void {
2023-03-08 03:23:11 +00:00
const test_step = b.step("test", "Test it");
b.default_step = test_step;
2023-03-08 03:23:11 +00:00
add(b, test_step, .Debug);
add(b, test_step, .ReleaseFast);
add(b, test_step, .ReleaseSmall);
add(b, test_step, .ReleaseSafe);
}
fn add(b: *std.Build, test_step: *std.Build.Step, optimize: std.builtin.OptimizeMode) void {
const target: std.zig.CrossTarget = .{ .os_tag = .macos };
2023-03-08 03:23:11 +00:00
testUnwindInfo(b, test_step, optimize, target, false, "no-dead-strip");
testUnwindInfo(b, test_step, optimize, target, true, "yes-dead-strip");
}
fn testUnwindInfo(
b: *std.Build,
test_step: *std.Build.Step,
2023-01-31 04:39:43 +00:00
optimize: std.builtin.OptimizeMode,
target: std.zig.CrossTarget,
dead_strip: bool,
2023-03-08 03:23:11 +00:00
name: []const u8,
) void {
2023-03-08 03:23:11 +00:00
const exe = createScenario(b, optimize, target, name);
exe.link_gc_sections = dead_strip;
re-enable test-cases and get them all passing Instead of using `zig test` to build a special version of the compiler that runs all the test-cases, the zig build system is now used as much as possible - all with the basic steps found in the standard library. For incremental compilation tests (the ones that look like foo.0.zig, foo.1.zig, foo.2.zig, etc.), a special version of the compiler is compiled into a utility executable called "check-case" which checks exactly one sequence of incremental updates in an independent subprocess. Previously, all incremental and non-incremental test cases were done in the same test runner process. The compile error checking code is now simpler, but also a bit rudimentary, and so it additionally makes sure that the actual compile errors do not include *extra* messages, and it makes sure that the actual compile errors output in the same order as expected. It is also based on the "ends-with" property of each line rather than the previous logic, which frankly I didn't want to touch with a ten-meter pole. The compile error test cases have been updated to pass in light of these differences. Previously, 'error' mode with 0 compile errors was used to shoehorn in a different kind of test-case - one that only checks if a piece of code compiles without errors. Now there is a 'compile' mode of test-cases, and 'error' must be only used when there are greater than 0 errors. link test cases are updated to omit the target object format argument when calling checkObject since that is no longer needed. The test/stage2 directory is removed; the 2 files within are moved to be directly in the test/ directory.
2023-03-10 01:22:51 +00:00
const check = exe.checkObject();
check.checkStart("segname __TEXT");
check.checkNext("sectname __gcc_except_tab");
check.checkNext("sectname __unwind_info");
switch (builtin.cpu.arch) {
.aarch64 => {
check.checkNext("sectname __eh_frame");
},
.x86_64 => {}, // We do not expect `__eh_frame` section on x86_64 in this case
else => unreachable,
}
check.checkInSymtab();
check.checkNext("{*} (__TEXT,__text) external ___gxx_personality_v0");
const run = b.addRunArtifact(exe);
run.skip_foreign_checks = true;
run.expectStdOutEqual(
\\Constructed: a
\\Constructed: b
\\About to destroy: b
\\About to destroy: a
\\Error: Not enough memory!
\\
);
test_step.dependOn(&run.step);
}
fn createScenario(
b: *std.Build,
optimize: std.builtin.OptimizeMode,
target: std.zig.CrossTarget,
2023-03-08 03:23:11 +00:00
name: []const u8,
) *std.Build.Step.Compile {
2023-01-31 04:39:43 +00:00
const exe = b.addExecutable(.{
2023-03-08 03:23:11 +00:00
.name = name,
2023-01-31 04:39:43 +00:00
.optimize = optimize,
.target = target,
});
b.default_step.dependOn(&exe.step);
exe.addIncludePath(".");
exe.addCSourceFiles(&[_][]const u8{
"main.cpp",
"simple_string.cpp",
"simple_string_owner.cpp",
}, &[0][]const u8{});
exe.linkLibCpp();
return exe;
}