public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@linuxcare.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] avoiding float underflow software assist
Date: Mon, 09 Oct 2000 16:44:29 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205561@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205556@msgid-missing>

>>>>> "Pete" = Pete Wyckoff <pw@osc.edu> writes:

Pete> Dan.Pop@cern.ch said:
>> On Mon, 9 Oct 2000, Pete Wyckoff wrote: > This little code snippet
>> causes floating-point underflow during the > multiplication.  Try
>> this code and see if it helps.  You don't have to explicitly call
>> the function, it will be automatically executed before main().

Pete> Excellent.  I can manage to get this linked in with the fortran
Pete> application from whence the problem sprung, which is what I
Pete> really wanted.

Pete> Gcc and glibc seem only to care about st0.  The "minimal" fix,
Pete> which relies on glibc and exercises its fe*env functions, is:

We discussed this recently and David strongly opted for glibc setting
s2/s3 the same way we set s0. I need to look closer at this in order
to figure out how to deal with the get-then-set case but I think it's
coming.

Some of this may be broken in glibc-2.1 which I believe is in the
Turbo distrib you are using, however glibc-2.1 is most likely not
going to get fixed.

Jes


  parent reply	other threads:[~2000-10-09 16:44 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 [this message]
2000-10-09 17:21 ` Dan Pop
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-105590678205561@msgid-missing \
    --to=jes@linuxcare.com \
    --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