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 tree-optimization/68097] We should track ranges for floating-point values too
Date: Thu, 17 Nov 2022 08:54:00 +0000	[thread overview]
Message-ID: <bug-68097-4-Hsd4kvgRfz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-68097-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 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:822a0823c012b912f0108a4da257cd97cbcdb7a3

commit r13-4125-g822a0823c012b912f0108a4da257cd97cbcdb7a3
Author: Aldy Hernandez <aldyh@redhat.com>
Date:   Sat Nov 12 11:58:07 2022 +0100

    [PR68097] Try to avoid recursing for floats in
gimple_stmt_nonnegative_warnv_p.

    It irks me that a PR named "we should track ranges for floating-point
    hasn't been closed in this release.  This is an attempt to do just
    that.

    As mentioned in the PR, even though we track ranges for floats, it has
    been suggested that avoiding recursing through SSA defs in
    gimple_assign_nonnegative_warnv_p is also a goal.  This patch uses a
    global range query (no on-demand lookups, just global ranges and
    minimal folding) to determine if the range of a statement is known to
    be non-negative.

            PR tree-optimization/68097

    gcc/ChangeLog:

            * gimple-fold.cc (gimple_stmt_nonnegative_warnv_p): Call
            range_of_stmt for floats.

  parent reply	other threads:[~2022-11-17  8:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26  8:48 [Bug tree-optimization/68097] New: " rsandifo at gcc dot gnu.org
2015-10-26  8:50 ` [Bug tree-optimization/68097] " pinskia at gcc dot gnu.org
2015-10-26 10:36 ` glisse at gcc dot gnu.org
2015-10-26 11:37 ` rguenth at gcc dot gnu.org
2015-10-27 11:53 ` rsandifo at gcc dot gnu.org
2022-09-17 12:10 ` aldyh at gcc dot gnu.org
2022-09-19  7:03 ` rguenth at gcc dot gnu.org
2022-09-19  7:31 ` aldyh at gcc dot gnu.org
2022-09-20 17:36 ` cvs-commit at gcc dot gnu.org
2022-11-08 15:57 ` aldyh at gcc dot gnu.org
2022-11-17  8:54 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-17  8:54 ` aldyh at gcc dot gnu.org
2022-11-28 22:24 ` 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-68097-4-Hsd4kvgRfz@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).