From: Richard Henderson <rth@twiddle.net>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: libc-ports@sourceware.org, linux-arm-kernel@lists.infradead.org
Subject: Re: Detecting support for trapping floating-point exceptions on ARM
Date: Wed, 27 Jun 2012 17:58:00 -0000 [thread overview]
Message-ID: <4FEB49B3.2030602@twiddle.net> (raw)
In-Reply-To: <Pine.LNX.4.64.1206121900150.1359@digraph.polyomino.org.uk>
On 06/12/2012 12:11 PM, Joseph S. Myers wrote:
> ARM VFPv3 and VFPv4 do not support trapping floating-point exceptions;
> VFPv2, VFPv3U and VFPv4U do. The lack of support causes the glibc
> math/test-fenv test to fail on VFPv3 and VFPv4 systems.
>
> The natural fix for that would be for fesetenv (FE_NOMASK_ENV) to fail on
> hardware not supporting trapping exceptions. There is, however, no HWCAP
> bit to indicate whether trapping floating-point exceptions is supported.
> Could one be added to the kernel, or is there a good way fesetenv could
> detect this from userspace without a new HWCAP bit?
I don't suppose those SBZ/RAZ bits just so happen to be ignored in
actual hardware, so that you can write 1 and read it back and get 0
to see if exceptions are unsupported?
Yes, that violates the spec as written, but if it just so happens to
work in current hardware that might be good enough convince someone
to adjust the spec to be slightly more handy.
r~
next prev parent reply other threads:[~2012-06-27 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 19:11 Joseph S. Myers
2012-06-27 17:58 ` Richard Henderson [this message]
2012-06-27 19:17 ` Joseph S. Myers
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=4FEB49B3.2030602@twiddle.net \
--to=rth@twiddle.net \
--cc=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=linux-arm-kernel@lists.infradead.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).