From: Steve ROBBINS <stever@bic.mni.mcgill.ca>
To: gsl-discuss@sources.redhat.com
Subject: looking for info on intel FPU status word
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <20010922152940.A23267@bottom.bic.mni.mcgill.ca> (raw)
Hello,
The GSL manual has a nice section on IEEE floating point
and on debugging numerical programs. That was quite informative,
but now that I know about GDB's "info float", I need help
to decipher its output :-)
In brief: my program is getting killed by SIGFPE and I want
to know why. With the help of the debugger and the core
file, I can get a lot of info, e.g.
(gdb) info float
R7: Valid 0x407eae650aca83660000 +2.318103121181380906e+38
R6: Empty 0x405fbb2c9c628c121000
R5: Valid 0x4024a9d39c27d0a70000 +182349924852.1630859
R4: Special 0x407eae650aca83660000 +2.318103121181380906e+38
R3: Empty 0x407eec0030dc78496800
R2: Empty 0x407ddc09d81377b99800
R1: Empty 0x407d895ade34733f1800
=>R0: Valid 0x407f82a65ec7673d7000 +3.473269661508283157e+38
Status Word: 0x00f0 UE PE ES SF
TOP: 0
Control Word: 0x0272 DM UM PM
PC: Double Precision (53-bits)
RC: Round to nearest
...
But I don't know what the abbreviations "UE", "PE", etc all mean.
I can guess, but I'd rather read a short document summarizing
the FPU status bits, etc.
I am working with an intel Pentium II in the above example, but I
also work on SGI machines, so help in both cases would be appreciated.
Thanks,
-S
next reply other threads:[~2001-12-19 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 13:20 Steve ROBBINS [this message]
2001-12-19 13:20 ` Brian Gough
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=20010922152940.A23267@bottom.bic.mni.mcgill.ca \
--to=stever@bic.mni.mcgill.ca \
--cc=gsl-discuss@sources.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).