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: [parisc-linux] fenv laid to rest, 50% done porting dbl-64 to ldbl-64, no testing yet.
Date: Mon, 20 Oct 2003 13:34:40 -0400	[thread overview]
Message-ID: <20031020173440.GE32666@systemhalted> (raw)
In-Reply-To: <200310201656.h9KGuAew001566@hiauly1.hia.nrc.ca>

On Mon, Oct 20, 2003 at 12:56:10PM -0400, John David Anglin wrote:
> > > 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?
> > 
> > Does this help?  The standard says
> > 
> > "Whether the feraiseexcept function additionally raises the inexact
> > exception whenever it raises the overflow or underflow exceptions is
> > implementation defined."
> 
> Also, in F.7.6.2,
> 
> "If the argument to the feraiseexcept function in <fenv.h> represents
> IEC 60559 valid coincident exceptions for atomic operations (namely
> overflow and inexact, or underflow and inexact) then overflow or
> underflow is raised before inexact."

Yes, I have already taken this into account. Thanks for all the help
with spec interpretation. I appreciate the feedback. We pass all the
fenv tests in glibc, but still fail the long double support. I'm about
50% done porting dbl-64 to ldbl-64, might get done in the next few 
weeks. It would finally give us a functioning long double :)

c.

  reply	other threads:[~2003-10-20 17:38 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
2003-10-20 16:31         ` John David Anglin
2003-10-20 16:56           ` John David Anglin
2003-10-20 17:34             ` Carlos O'Donell [this message]
2003-10-20 17:49               ` [parisc-linux] fenv laid to rest, 50% done porting dbl-64 to ldbl-64, no testing yet 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=20031020173440.GE32666@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.