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 c++/107732] ICE in lower_bound, at value-range.h:350 Date: Thu, 17 Nov 2022 17:43:25 +0000 [thread overview] Message-ID: <bug-107732-4-pvQa6GJ714@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107732-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107732 --- Comment #4 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:4e306222f442f8d4c6fc6da997ab756a5e43e36e commit r13-4131-g4e306222f442f8d4c6fc6da997ab756a5e43e36e Author: Aldy Hernandez <aldyh@redhat.com> Date: Thu Nov 17 16:47:17 2022 +0100 [PR tree-optimization/107732] [range-ops] Handle attempt to abs() negatives. The threader is creating a scenario where we are trying to solve: [NEGATIVES] = abs(x) While solving this we have an intermediate value of UNDEFINED because we have no positive numbers. But then we try to union the negative pair to the final result by querying the bounds. Since neither UNDEFINED nor NAN have bounds, they need to be specially handled. PR tree-optimization/107732 gcc/ChangeLog: * range-op-float.cc (foperator_abs::op1_range): Early exit when result is undefined. gcc/testsuite/ChangeLog: * gcc.dg/tree-ssa/pr107732.c: New test.
next prev parent reply other threads:[~2022-11-17 17:43 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-17 8:36 [Bug c++/107732] New: " gcc-bugzilla at al42and dot me 2022-11-17 15:12 ` [Bug c++/107732] " aldyh at gcc dot gnu.org 2022-11-17 15:54 ` aldyh at gcc dot gnu.org 2022-11-17 16:24 ` gcc-bugzilla at al42and dot me 2022-11-17 16:25 ` aldyh at gcc dot gnu.org 2022-11-17 17:43 ` cvs-commit at gcc dot gnu.org [this message] 2022-11-17 17:45 ` aldyh at gcc dot gnu.org 2022-11-28 22:25 ` [Bug c++/107732] [13 Regreession] " pinskia 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-107732-4-pvQa6GJ714@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: linkBe 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).