From: Dan Pop <Dan.Pop@cern.ch>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] avoiding float underflow software assist
Date: Mon, 09 Oct 2000 17:21:01 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205562@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205556@msgid-missing>
On Mon, 9 Oct 2000, David Mosberger wrote:
> >>>>> On Mon, 9 Oct 2000 17:37:35 +0200 (MET DST), Dan Pop <Dan.Pop@cern.ch> said:
>
> Dan> #include <asm/fpu.h>
>
> Please don't do this. Applications must not include Linux kernel
> header files.
I know. I wrote it as a quick and dirty hack for Sverre, because no
other option was available at the time.
> The correct way of doing this is to do:
>
> #include <fenv.h>
>
> fesetenv (FE_NONIEEE_ENV);
I know that, too, but, between the above hack that worked and the
correct solution that was not (yet) implemented, the choice was
obvious :-)
> or to compile with -ffast-math. For the former to work, you need
> glibc-2.2. For the latter, you need both glibc-2.2 and some mods to
> the compiler (which probably don't exist yet).
In other words, neither of the correct solutions is available with the
current distributions :-)
> If you want to avoid the those complications, you can turn off
> flush-to-zero mode with the following hack:
>
> asm volatile ("mov ar.fpsr=%0" :: "r"(0x9804c0270037f));
>
> It's only a hack, but it should do for now.
As a hack, it's even worse than mine :-)
Dan
next prev parent reply other threads:[~2000-10-09 17:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-09 15:12 [Linux-ia64] avoiding float underflow software assist Pete Wyckoff
2000-10-09 15:23 ` Saxena, Sunil
2000-10-09 15:37 ` Dan Pop
2000-10-09 16:02 ` David Mosberger
2000-10-09 16:03 ` Pete Wyckoff
2000-10-09 16:44 ` Jes Sorensen
2000-10-09 17:21 ` Dan Pop [this message]
2000-10-09 17:31 ` David Mosberger
2000-10-11 23:10 ` Pete Wyckoff
2000-10-12 16:13 ` Jes Sorensen
2000-10-17 22:40 ` Cary Coutant
2000-10-17 22:53 ` Cary Coutant
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=marc-linux-ia64-105590678205562@msgid-missing \
--to=dan.pop@cern.ch \
--cc=linux-ia64@vger.kernel.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