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/96392] Optimize x+0.0 if x is an integer
Date: Fri, 11 Jun 2021 16:18:34 +0000	[thread overview]
Message-ID: <bug-96392-4-2vAmhrFiqn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96392-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Roger Sayle <sayle@gcc.gnu.org>:

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

commit r12-1393-g5b02ed4b87685c0f7c5da9b46cde3ce56fcfd457
Author: Roger Sayle <roger@nextmovesoftware.com>
Date:   Fri Jun 11 17:15:38 2021 +0100

    [PATCH] PR tree-optimization/96392 Optimize x+0.0 if x is an integer

    The patch implements a missed optimization enhancement.  Under usual
    IEEE rules, x+0.0 can't be simplified to x when x might potentially
    be an IEEE minus zero (-0.0).  The current logic in the middle-end
    checks whether the type of x should honor signed zeros, but with this
    patch we introduce tree_expr_maybe_real_minus_zero_p that allows us
    to confirm that the value can't possibly be -0.0, for example, the result
    of a conversion from an integer type, or the result of fabs (or has a
    type that doesn't honor signed zero).

    Whilst modifying match.pd, I also converted some additional folding
    transformations from "testing the type" to "testing the value".

    2020-06-10  Roger Sayle  <roger@nextmovesoftware.com>

    gcc/ChangeLog
            PR tree-optimization/96392
            * fold-const.c (fold_real_zero_addition_p): Take both arguments
            of the addition or subtraction, not just the zero.  Use this
            other argument in tests for signaling NaNs and signed zeros.
            (tree_expr_maybe_real_minus_zero_p): New predicate.
            * fold-const.h (fold_real_zero_addition_p): Update prototype.
            (tree_expr_maybe_real_minus_zero_p): New function prototype.
            * match.pd: Update calls to fold_real_zero_addition_p.
            Replace HONOR_NANS with tree_expr_maybe_nan_p.
            Replace HONOR_SIGNED_ZEROS with tree_expr_maybe_real_minus_zero_p.
            Replace HONOR_SNANS with tree_expr_maybe_signaling_nan_p.
            * tree-ssa-reassoc.c (eliminate_using_constants): Update
            call to fold_real_zero_addition_p.

    gcc/testsuite/ChangeLog
            PR tree-optimization/96392
            * gcc.dg/pr96392.c: New test.

  parent reply	other threads:[~2021-06-11 16:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-30 19:08 [Bug tree-optimization/96392] New: " hugo_musso_gualandi at hotmail dot com
2020-07-30 20:34 ` [Bug tree-optimization/96392] " glisse at gcc dot gnu.org
2021-06-11 16:18 ` cvs-commit at gcc dot gnu.org [this message]
2021-06-11 16:43 ` cvs-commit at gcc dot gnu.org
2021-07-10  8:37 ` roger at nextmovesoftware dot com
2022-02-09 14:24 ` cvs-commit 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-96392-4-2vAmhrFiqn@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).