public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Michael Hudson-Doyle <michael.hudson@canonical.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v3] Avoid undefined behaviour in ibm128 implementation of llroundl (BZ #29488)
Date: Tue, 11 Oct 2022 10:48:51 +1300	[thread overview]
Message-ID: <CAJ8wqtff_e-jX5gyPr1Sea8hNntJbjgXhDUDzqTUSbZ3mdo51A@mail.gmail.com> (raw)
In-Reply-To: <20221010060050.3741173-1-aurelien@aurel32.net>

[-- Attachment #1: Type: text/plain, Size: 2454 bytes --]

On Mon, 10 Oct 2022 at 19:01, Aurelien Jarno <aurelien@aurel32.net> wrote:

> Detecting an overflow edge case depended on signed overflow of a long
> long. Replace the additions and the overflow checks by
> __builtin_add_overflow().
>

This certainly looks better than my fix, thanks!

Cheers,
mwh


>  sysdeps/ieee754/ldbl-128ibm/s_llroundl.c | 21 +++++++++------------
>  1 file changed, 9 insertions(+), 12 deletions(-)
>
> This patch is based on the original patch from Michael Hudson-Doyle,
> using __builtin_add_overflow() as suggested by Florian Weimer
>
> It passes all tests on ppc64el with gcc 12 with both -O2 and -O3.
>
> diff --git a/sysdeps/ieee754/ldbl-128ibm/s_llroundl.c
> b/sysdeps/ieee754/ldbl-128ibm/s_llroundl.c
> index d85154e73a..d8c0de1faf 100644
> --- a/sysdeps/ieee754/ldbl-128ibm/s_llroundl.c
> +++ b/sysdeps/ieee754/ldbl-128ibm/s_llroundl.c
> @@ -66,38 +66,35 @@ __llroundl (long double x)
>        /* Peg at max/min values, assuming that the above conversions do so.
>           Strictly speaking, we can return anything for values that
> overflow,
>           but this is more useful.  */
> -      res = hi + lo;
> -
> -      /* This is just sign(hi) == sign(lo) && sign(res) != sign(hi).  */
> -      if (__glibc_unlikely (((~(hi ^ lo) & (res ^ hi)) < 0)))
> +      if (__glibc_unlikely (__builtin_add_overflow (hi, lo, &res)))
>         goto overflow;
>
>        xh -= lo;
>        ldbl_canonicalize (&xh, &xl);
>
> -      hi = res;
>        if (xh > 0.5)
>         {
> -         res += 1;
> +         if (__glibc_unlikely (__builtin_add_overflow (res, 1, &res)))
> +           goto overflow;
>         }
>        else if (xh == 0.5)
>         {
>           if (xl > 0.0 || (xl == 0.0 && res >= 0))
> -           res += 1;
> +           if (__glibc_unlikely (__builtin_add_overflow (res, 1, &res)))
> +             goto overflow;
>         }
>        else if (-xh > 0.5)
>         {
> -         res -= 1;
> +         if (__glibc_unlikely (__builtin_add_overflow (res, -1, &res)))
> +           goto overflow;
>         }
>        else if (-xh == 0.5)
>         {
>           if (xl < 0.0 || (xl == 0.0 && res <= 0))
> -           res -= 1;
> +           if (__glibc_unlikely (__builtin_add_overflow (res, -1, &res)))
> +             goto overflow;
>         }
>
> -      if (__glibc_unlikely (((~(hi ^ (res - hi)) & (res ^ hi)) < 0)))
> -       goto overflow;
> -
>        return res;
>      }
>    else
> --
> 2.35.1
>
>

  reply	other threads:[~2022-10-10 21:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-10  6:00 Aurelien Jarno
2022-10-10 21:48 ` Michael Hudson-Doyle [this message]
2022-10-22 10:14 ` Aurelien Jarno
2022-10-24 13:55   ` 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=CAJ8wqtff_e-jX5gyPr1Sea8hNntJbjgXhDUDzqTUSbZ3mdo51A@mail.gmail.com \
    --to=michael.hudson@canonical.com \
    --cc=aurelien@aurel32.net \
    --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).