NetBSD Problem Report #59282

From www@netbsd.org  Sat Apr 12 17:37:08 2025
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256
	 client-signature RSA-PSS (2048 bits) client-digest SHA256)
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 7BA931A923E
	for <gnats-bugs@gnats.NetBSD.org>; Sat, 12 Apr 2025 17:37:08 +0000 (UTC)
Message-Id: <20250412173707.17C721A923F@mollari.NetBSD.org>
Date: Sat, 12 Apr 2025 17:37:07 +0000 (UTC)
From: campbell+netbsd@mumble.net
Reply-To: campbell+netbsd@mumble.net
To: gnats-bugs@NetBSD.org
Subject: pmax testbed runs in flush-to-zero mode
X-Send-Pr-Version: www-1.0

>Number:         59282
>Category:       misc
>Synopsis:       pmax testbed runs in flush-to-zero mode
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    misc-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Apr 12 17:40:00 +0000 2025
>Originator:     Taylor R Campbell
>Release:        current
>Organization:
The PmaxFTZ Foundation
>Environment:
>Description:
*** Check failed: /tmp/build/2025.04.11.04.54.02-pmax/src/tests/lib/libc/gen/t_fpclassify.c:149: fpclassify(d1) != FP_SUBNORMAL: [1] fpclassify(0x0p+0)=4 FP_SUBNORMAL=3
*** Check failed: /tmp/build/2025.04.11.04.54.02-pmax/src/tests/lib/libc/gen/t_fpclassify.c:152: [1] d1=0x0p+0 d0=0x1p-1022
...

https://releng.netbsd.org/b5reports/pmax/2025/2025.04.11.04.54.02/test.html#lib_libc_gen_t_fpclassify_fpclassify_double

d1 at this point is the result of DBL_MIN/2, which should be subnormal (FP_SUBNORMAL=3), not zero (FP_ZERO=4).  So this machine appears to be running in flush-to-zero mode, or can't distinguish between subnormal and zero operands.
>How-To-Repeat:
cd /usr/tests/lib/libc/gen
atf-run t_fpclassify | atf-report
>Fix:
Yes, please!

Not sure if this is a qemu bug or a hardware bug or a NetBSD kernel bug in configuring the FPU.

Home	PR Database Search