authorgravatar for andrew@ziglang.orgAndrew Kelley <andrew@ziglang.org> 2020-11-06 18:58:10-07:00
committergravatar for andrew@ziglang.orgAndrew Kelley <andrew@ziglang.org> 2020-11-06 18:58:10-07:00
log67ea47babdb891b7775b68683b232aa3c97ea012
treeeba067223d5c7c720a45016d0d546002dad59092
parent663f0b399c5f4e2528a969fba6cd58d8f9784f5a

Revert "update runtime safety test case - unsigned-signed vector cast"

This reverts commit 663f0b399c5f4e2528a969fba6cd58d8f9784f5a. The behavior appears to be inconsistent between running locally and on the CI. I suspect it could be based on what vector CPU features are available.

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

test/runtime_safety.zig+1-1
...@@ -89,7 +89,7 @@ pub fn addCases(cases: *tests.CompareOutputContext) void {...@@ -89,7 +89,7 @@ pub fn addCases(cases: *tests.CompareOutputContext) void {
89 \\const std = @import("std");89 \\const std = @import("std");
90 \\const V = @import("std").meta.Vector;90 \\const V = @import("std").meta.Vector;
91 \\pub fn panic(message: []const u8, stack_trace: ?*@import("builtin").StackTrace) noreturn {91 \\pub fn panic(message: []const u8, stack_trace: ?*@import("builtin").StackTrace) noreturn {
92 \\ if (std.mem.eql(u8, message, "integer cast truncated bits")) {92 \\ if (std.mem.eql(u8, message, "attempt to cast negative value to unsigned integer")) {
93 \\ std.process.exit(126); // good93 \\ std.process.exit(126); // good
94 \\ }94 \\ }
95 \\ std.process.exit(0); // test failed95 \\ std.process.exit(0); // test failed