public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Paul E. Murphy" <murphyp@linux.vnet.ibm.com>
To: libc-alpha@sourceware.org
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: [PATCH] powerpc: Cleanup fenv_private.h
Date: Fri, 10 Jun 2016 21:47:00 -0000	[thread overview]
Message-ID: <d85cf782-ac5a-f6ee-ee24-6bb794231102@linux.vnet.ibm.com> (raw)
In-Reply-To: <575B2229.7070605@linaro.org>



On 06/10/2016 03:25 PM, Adhemerval Zanella wrote:
> It seems a nice cleanup and about the wrong code, I presume it is
> the one that might use _FPU_MASK_FRAC_INEX_RET_CC (which was indeed
> wrongly defined). Does it trigger any user visible issue in math
> tests?

I didn't see any.  Joseph has done a good job fixing them with the
slew of new test cases he has been adding.  This was the result of my
attempt to understand how all these macros fit together (or don't).

That mask was one minor issue.  Though, now that you point it out,
this does assume the DRN bits don't change.  I suppose one could
contrive a case where this might be problem.  Though, this patch
shouldn't change the status quo.

The more immediate issue was this macro and its usage:

-#define _FPU_MASK_ROUNDING 0xffffffff00000007LL

Which does not actually mask the roundings bits.  The pathologic
case being:

-  new.l = (old.l & _FPU_MASK_ROUNDING) | r;

Thus the resulting rounding mode may not always end up being the
desired one.  Though, as far as I can tell, both instances only
occur in functions that aren't used.

Likewise, as far as I could tell, the libc_feholdexcept_setround_ctx
macros are never used via any SET_RESTORE_* macros.

  reply	other threads:[~2016-06-10 21:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-10 19:50 Paul E. Murphy
2016-06-10 20:25 ` Adhemerval Zanella
2016-06-10 21:47   ` Paul E. Murphy [this message]
2016-10-05 15:10 ` Paul E. Murphy
2016-10-21 20:23 ` Tulio Magno Quites Machado Filho

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=d85cf782-ac5a-f6ee-ee24-6bb794231102@linux.vnet.ibm.com \
    --to=murphyp@linux.vnet.ibm.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).