c2db077574
Previously, std.debug.assert would `@panic` in test builds, if the assertion failed. Now, it's always `unreachable`. This makes release mode test builds more accurately test the actual code that will be run. However this requires tests to call `std.testing.expect` rather than `std.debug.assert` to make sure output is correct. Here is the explanation of when to use either one, copied from the assert doc comments: Inside a test block, it is best to use the `std.testing` module rather than assert, because assert may not detect a test failure in ReleaseFast and ReleaseSafe mode. Outside of a test block, assert is the correct function to use. closes #1304
23 lines
760 B
Zig
23 lines
760 B
Zig
const __fixunstfsi = @import("fixunstfsi.zig").__fixunstfsi;
|
|
const testing = @import("std").testing;
|
|
|
|
fn test__fixunstfsi(a: f128, expected: u32) void {
|
|
const x = __fixunstfsi(a);
|
|
testing.expect(x == expected);
|
|
}
|
|
|
|
const inf128 = @bitCast(f128, u128(0x7fff0000000000000000000000000000));
|
|
|
|
test "fixunstfsi" {
|
|
test__fixunstfsi(inf128, 0xffffffff);
|
|
test__fixunstfsi(0, 0x0);
|
|
test__fixunstfsi(0x1.23456789abcdefp+5, 0x24);
|
|
test__fixunstfsi(0x1.23456789abcdefp-3, 0x0);
|
|
test__fixunstfsi(0x1.23456789abcdefp+20, 0x123456);
|
|
test__fixunstfsi(0x1.23456789abcdefp+40, 0xffffffff);
|
|
test__fixunstfsi(0x1.23456789abcdefp+256, 0xffffffff);
|
|
test__fixunstfsi(-0x1.23456789abcdefp+3, 0x0);
|
|
|
|
test__fixunstfsi(0x1.p+32, 0xFFFFFFFF);
|
|
}
|