public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>
Cc: GNU C Library <libc-alpha@sourceware.org>, <nd@arm.com>
Subject: Re: [PATCH 1/6] Use uint32_t sign in single precision math error handling, functions
Date: Thu, 28 Jun 2018 17:15:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.20.1806281715310.16299@digraph.polyomino.org.uk> (raw)
In-Reply-To: <bb5159bb-d5d7-9e24-9b97-8ea6f70fc907@arm.com>

On Wed, 27 Jun 2018, Szabolcs Nagy wrote:

> Ideally sign should be bool, but sometimes (e.g. in powf) it's more
> efficient to pass a non-zero value than 1 to indicate that the sign
> should be set.  The fixed size int is less ambigous than unsigned
> long.
> 
> 2018-06-27  Szabolcs Nagy  <szabolcs.nagy@arm.com>
> 
>     * sysdeps/ieee754/flt-32/e_powf.c (__powf): Use uint32_t.
>     (exp2f_inline): Likewise.
>     * sysdeps/ieee754/flt-32/math_config.h (__math_oflowf): Likewise.
>     (__math_uflowf): Likewise.
>     (__math_may_uflowf): Likewise.
>     (__math_divzerof): Likewise.
>     (__math_invalidf): Likewise.
>     * sysdeps/ieee754/flt-32/math_errf.c (xflowf): Likewise.
>     (__math_oflowf): Likewise.
>     (__math_uflowf): Likewise.
>     (__math_may_uflowf): Likewise.
>     (__math_divzerof): Likewise.
>     (__math_invalidf): Likewise.

OK.

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2018-06-28 17:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27 14:52 Szabolcs Nagy
2018-06-28 17:15 ` Joseph Myers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-27 14:50 Szabolcs Nagy

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=alpine.DEB.2.20.1806281715310.16299@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=nd@arm.com \
    --cc=szabolcs.nagy@arm.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).