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
33 lines
1.0 KiB
Zig
33 lines
1.0 KiB
Zig
const __fixunstfti = @import("fixunstfti.zig").__fixunstfti;
|
|
const testing = @import("std").testing;
|
|
|
|
fn test__fixunstfti(a: f128, expected: u128) void {
|
|
const x = __fixunstfti(a);
|
|
testing.expect(x == expected);
|
|
}
|
|
|
|
const inf128 = @bitCast(f128, u128(0x7fff0000000000000000000000000000));
|
|
|
|
test "fixunstfti" {
|
|
test__fixunstfti(inf128, 0xffffffffffffffffffffffffffffffff);
|
|
|
|
test__fixunstfti(0.0, 0);
|
|
|
|
test__fixunstfti(0.5, 0);
|
|
test__fixunstfti(0.99, 0);
|
|
test__fixunstfti(1.0, 1);
|
|
test__fixunstfti(1.5, 1);
|
|
test__fixunstfti(1.99, 1);
|
|
test__fixunstfti(2.0, 2);
|
|
test__fixunstfti(2.01, 2);
|
|
test__fixunstfti(-0.01, 0);
|
|
test__fixunstfti(-0.99, 0);
|
|
|
|
test__fixunstfti(0x1.p+128, 0xffffffffffffffffffffffffffffffff);
|
|
|
|
test__fixunstfti(0x1.FFFFFEp+126, 0x7fffff80000000000000000000000000);
|
|
test__fixunstfti(0x1.FFFFFEp+127, 0xffffff00000000000000000000000000);
|
|
test__fixunstfti(0x1.FFFFFEp+128, 0xffffffffffffffffffffffffffffffff);
|
|
test__fixunstfti(0x1.FFFFFEp+129, 0xffffffffffffffffffffffffffffffff);
|
|
}
|