On Thu, Nov 30, 2017 at 06:16:10AM +0700, Robert Elz wrote: > Date: Wed, 29 Nov 2017 16:51:56 +0000 > From: Taylor R Campbell > <campbell+netbsd-source-change...@mumble.net> > Message-ID: <20171129165637.6fa4960...@jupiter.mumble.net> > > | This is starting to smell like a compiler bug in fp correctness...but > | I'm out of time to diagnose it further. > > In case anyone missed it, the i386 ATF test on b5 failed the exact same way > (same values) as my Xen DomU i386 test. But that was as expected I think. > > Since this has now devolved to a discussion of how i386 FP works, and > how the compiler generates code to use it, I'm out of this discussion from > here on (I will send a message on port-i386 and tech-userlevel to see if > someone with i386 FP knowledge can work out who/what is at fault here.) > > Unless someone finds a fix, or at least finds the source of the problem, > and files a PR, I will return this test to "succeeding" status (by "hiding" > the problem, as Joerg put it). This test is not the place to diagnose either > compiler issues, or i386 floating point issues. If we need a test for those, > please add one - elsewhere.
Shouldn't it be made Xfail on i386 in this case ? -- Manuel Bouyer <bou...@antioche.eu.org> NetBSD: 26 ans d'experience feront toujours la difference --