authorgravatar for hi@mihaelm.commihael <hi@mihaelm.com> 2026-03-20 18:03:36+01:00
committergravatar for hi@mihaelm.commihael <hi@mihaelm.com> 2026-04-02 23:54:19+02:00
loge15d8dd3d27047043a371421e59bc11c83a7a1b5
tree786d2828d7bde2e387512ae4cb4bd03af1836947
parent2cbd6980e5a06ce4a2828a10b6cdb0efba827f84
signaturebadge-check Signed by SSH key SHA256:aoFoShdYLdrqMichqKXSSieTKUfACUIDJHsKc4V2tQg

`libc-test/math`: Enable `rint` tests

The `rint` tests were commented out when added along with other functions to the `libc-test` runner, presumably because they were failing. In the meantime, we moved to using a Zig-implemented `rint` and I found that the tests are now passing. To celebrate, I'm putting them back into commission. Having these tests in a working state is nice because functions like `lrint`, `llrint`, and `nearbyint` depend on `rint` implementation being correct. Results: ``` $ ./build/stage3/bin/zig build -p stage4 -Denable-llvm -Dno-lib $ stage4/bin/zig build test-libc -Dlibc-test-path=<LIBC-TEST-PATH> -Dtest-filter=rint -fqemu -fwasmtime --summary line Build Summary: 2209/2209 steps succeeded ```

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

test/libc.zig+1-1
......@@ -293,7 +293,7 @@ pub fn addCases(cases: *tests.LibcContext) void {
293293 cases.addLibcTestCase("math/remquo.c", true, .{});
294294 cases.addLibcTestCase("math/remquof.c", true, .{});
295295 cases.addLibcTestCase("math/remquol.c", true, .{});
296 // cases.addLibcTestCase("math/rint.c", true, .{});
296 cases.addLibcTestCase("math/rint.c", true, .{});
297297 cases.addLibcTestCase("math/rintf.c", true, .{});
298298 // cases.addLibcTestCase("math/rintl.c", true, .{});
299299 cases.addLibcTestCase("math/round.c", true, .{});