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 middle-end/107355] [13 Regression] ICE: in lower_bound, at value-range.h:350 with -fsanitize=float-cast-overflow since r13-3231-g706d8583706475fb
Date: Mon, 24 Oct 2022 13:33:58 +0000	[thread overview]
Message-ID: <bug-107355-4-iChddzXh42@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107355-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Aldy Hernandez <aldyh@gcc.gnu.org>:

https://gcc.gnu.org/g:5bcd92d0d4029f3d1d2eacc0e2bff1685545b74f

commit r13-3456-g5bcd92d0d4029f3d1d2eacc0e2bff1685545b74f
Author: Aldy Hernandez <aldyh@redhat.com>
Date:   Mon Oct 24 12:37:25 2022 +0200

    [PR tree-optimization/107355] Handle NANs in abs range-op entry.

    The problem here is that the threader is coming up with a path where
    the only valid result is a NAN.  When the abs op1_range entry is
    trying to add the negative posibility, it attempts to get the bounds
    of the working range.  NANs don't have bounds so they need to be
    special cased.

            PR tree-optimization/107355

    gcc/ChangeLog:

            * range-op-float.cc (foperator_abs::op1_range): Handle NAN.

    gcc/testsuite/ChangeLog:

            * gcc.dg/tree-ssa/pr107355.c: New test.

  parent reply	other threads:[~2022-10-24 13:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-22  5:24 [Bug middle-end/107355] New: [13 Regression] ICE: in lower_bound, at value-range.h:350 with -fsanitize=float-cast-overflow zsojka at seznam dot cz
2022-10-24  7:14 ` [Bug middle-end/107355] [13 Regression] ICE: in lower_bound, at value-range.h:350 with -fsanitize=float-cast-overflow since r13-3231-g706d8583706475fb marxin at gcc dot gnu.org
2022-10-24 10:38 ` aldyh at gcc dot gnu.org
2022-10-24 13:00 ` rguenth at gcc dot gnu.org
2022-10-24 13:33 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-24 13:35 ` aldyh at gcc dot gnu.org
2022-10-24 13:35 ` aldyh 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-107355-4-iChddzXh42@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).