From: Aldy Hernandez <aldyh@redhat.com>
To: rth@redhat.com, gcc@gcc.gnu.org
Subject: ieee.exp tests containing generic FP tests
Date: Fri, 15 Oct 2004 20:39:00 -0000 [thread overview]
Message-ID: <20041015191645.GA11010@redhat.com> (raw)
Hi Richard. Hi folks.
Most of the tests in execute/ieee/ fail on the e500 (and the Vax for
that matter), but there are a handful that pass, and which I don't
consider IEEE compliance tests.
Could someone more IEEE savvy point out which tests could be moved one
level higher (gcc.c-torture/execute). I volunteer to move them,
I'm just not sure whether all the ones I think should be moved, should...
In particular, I believe we should keep all the INF, NAN, PZERO,
NZERO, *ORDERED, tests in ieee/ and move everything else out.
For example, these are a few I believe don't belong in IEEE:
20001122-1.c
20010114-2.c
20011123-1.c
20030331-1.c
acc1.c
etc.
OTOH, things like fp-cmp*, mzero*, compare-fp*, etc do obviously belong in
IEEE.
Agreed? Am I missing something?
Cheers.
Aldy
next reply other threads:[~2004-10-15 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 20:39 Aldy Hernandez [this message]
2004-10-15 23:44 ` Geoffrey Keating
2004-10-16 2:25 ` Aldy Hernandez
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041015191645.GA11010@redhat.com \
--to=aldyh@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.com \
/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).