All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: dave.anglin@nrc-cnrc.gc.ca, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: HPPA FPU Specification? (FE_INEXACT raised by accident)
Date: Mon, 20 Oct 2003 12:01:58 -0400	[thread overview]
Message-ID: <20031020160158.GC32666@systemhalted> (raw)
In-Reply-To: <200310201530.h9KFUYZN000693@hiauly1.hia.nrc.ca>

On Mon, Oct 20, 2003 at 11:30:34AM -0400, John David Anglin wrote:
> > > I suggest looking at page 10-7.  It describes the PA 2.0 behavior
> > > for this situation.  I'm not an IEEE so I don't know offhand what it
> > > mandates.
> > 
> > Multiple exceptions per instruction is not the intended behaviour :)
> > I need two numbers, that when added only overflow, not overflow and
> > inexact. The same to be said for underflow. Perhaps I just need to 
> > dig more.
> 
> Well 10-7 talks explicitly about what happens when you get both
> exceptions on a single instruction.  On the otherhand, the discussion
> of the inexact exception seems to imply that inexact should only occur
> in an overflow/underflow situation when an overflow/underflow exception
> doesn't occur.  Possibly, the PA implementation is not consistent with
> IEEE mandated behavior, but I can't be sure.

My reading of 10-7 and the equivalent sections in the PA 1.1 arch
doc indicate that it _can_ happen outside of an overflow/underflow
situation. It just so happens that it can also be coupled with
underflow/overflow exceptions.

Does having them both at the same time violates the behaviour of
"feraiseexcept" in the ISO C standard (especially in the case of
underflow)? If feraiseexcept is called and only an underflow 
requested, but underflow and inexact are enabled, what then?

c.

  reply	other threads:[~2003-10-20 16:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-19 21:51 [parisc-linux] HPPA FPU Specification? (FE_INEXACT raised by accident) Carlos O'Donell
2003-10-19 23:16 ` [parisc-linux] " John David Anglin
2003-10-20  5:02   ` Carlos O'Donell
2003-10-20 15:30     ` John David Anglin
2003-10-20 16:01       ` Carlos O'Donell [this message]
2003-10-20 16:31         ` John David Anglin
2003-10-20 16:56           ` John David Anglin
2003-10-20 17:34             ` [parisc-linux] fenv laid to rest, 50% done porting dbl-64 to ldbl-64, no testing yet Carlos O'Donell
2003-10-20 17:49               ` John David Anglin
2003-10-20 19:04                 ` Carlos O'Donell
2003-10-21 10:42                 ` Joel Soete
2003-10-21 17:31                   ` John David Anglin
2003-10-20 17:31           ` [parisc-linux] Re: HPPA FPU Specification? (FE_INEXACT raised by accident) Carlos O'Donell

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=20031020160158.GC32666@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=dave.anglin@nrc-cnrc.gc.ca \
    --cc=dave@hiauly1.hia.nrc.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.