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/105276] [12 Regression]  executed once loop not optimized anymore
Date: Mon, 25 Apr 2022 13:59:25 +0000	[thread overview]
Message-ID: <bug-105276-4-salD8eHrN3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105276-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Macleod <amacleod@gcc.gnu.org>:

https://gcc.gnu.org/g:362e2a9c6297203bcf7f66bfb51dffb82b42d3b3

commit r12-8246-g362e2a9c6297203bcf7f66bfb51dffb82b42d3b3
Author: Andrew MacLeod <amacleod@redhat.com>
Date:   Mon Apr 25 09:56:35 2022 -0400

    Retain existing range knowledge when prefilling statements.

    When range_of_stmt was adjusted to avoid large recursion depth, we need to
    intersect the calculated range whth the any known range to avoid losing
    info.  Range_of_stmt does this, but the new prefill code missed it.

            PR tree-optimization/105276
            gcc/
            * gimple-range.cc (gimple_ranger::prefill_stmt_dependencies):
Include
            existing global range with calculated value.

            gcc/testsuite/
            * g++.dg/pr105276.C: New.

  parent reply	other threads:[~2022-04-25 13:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 13:47 [Bug c/105276] New: " denis.campredon at gmail dot com
2022-04-19  8:29 ` [Bug tree-optimization/105276] " rguenth at gcc dot gnu.org
2022-04-20 15:38 ` jakub at gcc dot gnu.org
2022-04-21 15:46 ` amacleod at redhat dot com
2022-04-25 13:59 ` cvs-commit at gcc dot gnu.org [this message]
2022-04-25 14:27 ` amacleod at redhat dot com

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-105276-4-salD8eHrN3@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).