From: "Marijn Schouten (hkBst)" <hkBst@gentoo.org>
To: Greg Troxel <gdt@ir.bbn.com>
Cc: guile-devel@gnu.org
Subject: Re: math tests on amd64
Date: Fri, 20 Jun 2008 19:44:36 +0200 [thread overview]
Message-ID: <485BEC84.9000007@gentoo.org> (raw)
In-Reply-To: <rmi63s6y0si.fsf@fnord.ir.bbn.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Greg Troxel wrote:
> I ran 'make check' on guile on NetBSD-current on amd64, and got a
> failure:
>
> guile> (version)
> "1.8.5"
> guile> (eqv? 0.0 (exp -inf.0))
> #f
> guile> (exp -inf.0)
> +nan.0
On my amd64 linux system I get:
guile> (version)
"1.8.5"
guile> (eqv? 0.0 (exp -inf.0))
#t
guile> (exp -inf.0)
0.0
HTH, Marijn
> On i386 and sparc64 this passes. I ran paranoia and that passed (with
> not even flaws). Does this test pass for others on other operating
> systems on amd64? If so, I should look into whether it's a NetBSD bug,
> variance in floating point flags, or a guile bug.
>
> So far this looks like a failure of NetBSD on amd64 to follow POSIX:
> http://www.opengroup.org/onlinepubs/009695399/functions/exp.html
- --
Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-{lisp,ml} on FreeNode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkhb7IQACgkQp/VmCx0OL2z5YwCgjemUCb08v/nz4UZS4A/+7t0c
cVoAnjqrdEEfF07V/9YtSMgiyf5tSlQO
=YN+l
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-06-20 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 16:37 how does one debug a SEGV in scm_threads_prehistory? Bruce Korb
2008-06-18 19:29 ` Greg Troxel
2008-06-18 20:25 ` Bruce Korb
2008-06-19 18:09 ` Greg Troxel
2008-06-18 19:56 ` math tests on amd64 Greg Troxel
2008-06-19 13:18 ` Neil Jerram
2008-06-19 18:03 ` Greg Troxel
2008-06-20 17:44 ` Marijn Schouten (hkBst) [this message]
2008-06-19 13:14 ` how does one debug a SEGV in scm_threads_prehistory? Neil Jerram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=485BEC84.9000007@gentoo.org \
--to=hkbst@gentoo.org \
--cc=gdt@ir.bbn.com \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).