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/110204] [14 Regression] Suspicous warning when compiling ranges-v3 using GCC trunk (iteration 9223372036854775807 invokes undefined behavior)
Date: Thu, 20 Jul 2023 12:46:22 +0000	[thread overview]
Message-ID: <bug-110204-4-GAKPom4uUj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110204-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:d0de3bf9175877d6c51c94fe04662c6e031876e1

commit r14-2674-gd0de3bf9175877d6c51c94fe04662c6e031876e1
Author: Richard Biener <rguenther@suse.de>
Date:   Mon Jul 17 12:15:29 2023 +0200

    tree-optimization/110204 - second level redundancy and simplification

    When PRE discovers a full redundancy during insertion it cannot unite
    the two value sets.  Instead it inserts a copy old-val = new-val where
    new-val can also be a constant.  The following looks through such
    copies during elimination, providing one extra level of constant and
    copy propagation.  For the PR this helps avoiding a bogus diagnostic
    that's emitted on unreachable code during loop optimization.

            PR tree-optimization/110204
            * tree-ssa-sccvn.cc (eliminate_dom_walker::eliminate_avail):
            Look through copies generated by PRE.

  parent reply	other threads:[~2023-07-20 12:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-10 14:41 [Bug c++/110204] New: " jun at junz dot org
2023-06-10 15:54 ` [Bug tree-optimization/110204] " pinskia at gcc dot gnu.org
2023-06-10 15:54 ` [Bug tree-optimization/110204] [14 Regression] " pinskia at gcc dot gnu.org
2023-07-15  3:34 ` pinskia at gcc dot gnu.org
2023-07-15  3:48 ` pinskia at gcc dot gnu.org
2023-07-15  3:56 ` pinskia at gcc dot gnu.org
2023-07-17  9:55 ` rguenth at gcc dot gnu.org
2023-07-19 13:12 ` rguenth at gcc dot gnu.org
2023-07-20 12:46 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-20 12:55 ` rguenth 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-110204-4-GAKPom4uUj@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).