public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/114397] wrong code with _BitInt() division at -O0
Date: Thu, 21 Mar 2024 12:08:45 +0000	[thread overview]
Message-ID: <bug-114397-4-MnUjY92VsE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114397-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114397

--- Comment #2 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:59b6cece54f33ac4994834d01e18269856576556

commit r14-9592-g59b6cece54f33ac4994834d01e18269856576556
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Thu Mar 21 13:07:50 2024 +0100

    libgcc: Fix up bitint division [PR114397]

    The Knuth's division algorithm relies on the number of dividend limbs
    to be greater ore equal to number of divisor limbs, which is why
    I've added a special case for un < vn at the start of __divmodbitint4.
    Unfortunately, my assumption that it then implies abs(v) > abs(u) and
    so quotient must be 0 and remainder same as dividend is incorrect.
    This is because this check is done before negation of the operands.
    While bitint_reduce_prec reduces precision from clearly useless limbs,
    the problematic case is when the dividend is unsigned or non-negative
    and divisor is negative.  We can have limbs (from MS to LS):
    dividend:       0       M       ?...
    divisor:        -1      -N      ?...
    where M has most significant bit set and M >= N (if M == N then it
    also the following limbs matter) and the most significant limbs can
    be even partial.  In this case, the quotient should be -1 rather than
    0.  bitint_reduce_prec will reduce the precision of the dividend so
    that M is the most significant limb, but can't reduce precision of the
    divisor to more than having the -1 as most significant limb, because
    -N doesn't have the most significant bit set.

    The following patch fixes it by detecting this problematic case in the
    un < vn handling, and instead of assuming q is 0 and r is u will
    decrease vn by 1 because it knows the later code will negate the divisor
    and it can be then expressed after negation in one fewer limbs.

    2024-03-21  Jakub Jelinek  <jakub@redhat.com>

            PR libgcc/114397
            * libgcc2.c (__divmodbitint4): Don't assume un < vn always means
            abs(v) > abs(u), check for a special case of un + 1 == vn where
            u is non-negative and v negative and after v's negation vn could
            be reduced by 1.

            * gcc.dg/torture/bitint-65.c: New test.

  parent reply	other threads:[~2024-03-21 12:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 17:39 [Bug libgcc/114397] New: " zsojka at seznam dot cz
2024-03-20 17:53 ` [Bug libgcc/114397] " jakub at gcc dot gnu.org
2024-03-21 12:08 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-21 12:13 ` jakub at gcc dot gnu.org

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=bug-114397-4-MnUjY92VsE@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).