Date: Wed, 13 Oct 2021 09:00:44 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 224326] double subnormals are not well printed on printing with printf (and friends) Message-ID: <bug-224326-227-wtofOm5JDW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224326-227@https.bugs.freebsd.org/bugzilla/> References: <bug-224326-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224326 --- Comment #6 from Luis Colorado <luiscoloradourcola@gmail.com> --- arm64 is not the architecture I'm talking about, as the rpi 2+ is 32 bit ar= ch and not arm64. Anyway I suspect the problem will be also there, as both architectures will probably share the floating point unit. But you tell me that you are getting correct results in AMD64 (which is the intel 64 bit architecture, and not ARM at all) Sorry, but I don't get the point here. It is four years this bug is rolling over there. My impressio= n is that arm architectures don't support 64bit floating point subnormals at all, and that's the reason the software is failing, as it doesn't cut the thing = and makes them as 0 (which obviously the hardware is not doing) IMHO, the floating point library should check if the processor supports subnormals or not, which is something required by the ieee standard, and ro= und the values to 0.0, instead. That is easy to check, as the exponent field is all zeros for subnormals. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224326-227-wtofOm5JDW>