authorgravatar for kubkon@jakubkonka.comJakub Konka <kubkon@jakubkonka.com> 2023-01-20 21:27:54+01:00
committergravatar for kubkon@jakubkonka.comJakub Konka <kubkon@jakubkonka.com> 2023-01-20 21:27:57+01:00
logeb0c959b43f0581177299de53990be1a65e75947
treed6d9dcd4457c4d9ff50ac07e7dbee5cd2b3c820f
parente0ccbff87d329b607093f8f88f959e34571dac70

link-tests: update uuid test with new uuid values

Changes only pertain arm64 as for x86_64 turns out we are missing one additional feature which is synthesising unwind info from only eh frame records, or at least this is what it looks like when I analysed the output of Apple's ld.

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

test/link/macho/uuid/build.zig+3-3
...@@ -12,9 +12,9 @@ pub fn build(b: *Builder) void {...@@ -12,9 +12,9 @@ pub fn build(b: *Builder) void {
12 .os_tag = .macos,12 .os_tag = .macos,
13 };13 };
1414
15 testUuid(b, test_step, .ReleaseSafe, aarch64_macos, "af0f4c21a07c30daba59213d80262e45");15 testUuid(b, test_step, .ReleaseSafe, aarch64_macos, "675bb6ba8e5d3d3191f7936d7168f0e9");
16 testUuid(b, test_step, .ReleaseFast, aarch64_macos, "af0f4c21a07c30daba59213d80262e45");16 testUuid(b, test_step, .ReleaseFast, aarch64_macos, "675bb6ba8e5d3d3191f7936d7168f0e9");
17 testUuid(b, test_step, .ReleaseSmall, aarch64_macos, "af0f4c21a07c30daba59213d80262e45");17 testUuid(b, test_step, .ReleaseSmall, aarch64_macos, "675bb6ba8e5d3d3191f7936d7168f0e9");
1818
19 const x86_64_macos = std.zig.CrossTarget{19 const x86_64_macos = std.zig.CrossTarget{
20 .cpu_arch = .x86_64,20 .cpu_arch = .x86_64,