From: Randolph Chung <randolph@tausq.org>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Unknown FPU exception, help needed, please decode.
Date: Fri, 16 Dec 2005 07:54:59 +0800 [thread overview]
Message-ID: <43A20253.6080408@tausq.org> (raw)
In-Reply-To: <20051215192204.GE1298@baldric.uwo.ca>
> arch/parisc/math-emu/decode_exc.c(351) Unknown FPU exception 0x23
> arch/parisc/math-emu/decode_exc.c(351) Unknown FPU exception 0x23
> ...
>
> Could someone please decode the FPU exception and tell me if the kernel
> is doing the right thing?
From page 10-3 in the PA2.0 arch book, this seems to be the
"unimplemented" exception.
Pages 10-8 and 10-9 goes on to say:
A conversion to a floating poiint format always causes an unimplemented
exception when the result overflows, the result lies too far outside the
range for the exponent to be bias-adjusted, and the overflow trap is
enabled. [...]
Similarly, an unimplemented exception is always caused by a conversion
to a floating-point format that underflows, lies too far outside the
range for the exponent to be bias-adjusted, and the underflow trap is
enabled. [...]
Finally, the unimplemented exception is always signaled when the operand
of a conversion to an integer format is a NaN. Low-level trap handlers
may choose to silently deliver a result or convert it to an invalid
exception.
Do any of these apply to your test case?
randolph
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-12-15 23:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 19:22 [parisc-linux] Unknown FPU exception, help needed, please decode Carlos O'Donell
2005-12-15 23:54 ` Randolph Chung [this message]
2005-12-16 1:13 ` Carlos O'Donell
2005-12-16 2:33 ` Grant Grundler
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=43A20253.6080408@tausq.org \
--to=randolph@tausq.org \
--cc=carlos@systemhalted.org \
--cc=parisc-linux@lists.parisc-linux.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