public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106511] [13/14 Regression] New -Werror=maybe-uninitialized since r13-1268-g8c99e307b20c502e
Date: Wed, 06 Dec 2023 08:55:51 +0000	[thread overview]
Message-ID: <bug-106511-4-s6iJ7jgBYn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106511-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rguenth at gcc dot gnu.org

--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Andrew Macleod from comment #8)
> (In reply to Richard Biener from comment #2)
> > VRP could use max_stmt_executions here (note it doesn't properly handle loop
> > nests so the name is somewhat misleading)
> 
> Do you have to ask for max_stmt_executions on each loop nest for the stmt to
> get the real total?  and multiple them all together?  or can you only count
> on loop_outer()?

max_stmt_executions is for the loop you pass, not including outer loop
(or containing irreducible region) iterations.

The loop you usually pass is gimple_bb (stmt)->loop_father which is the
immediately containing loop.  This will be useful only when the PHI
we want to analyze is in the very same loop, if it is in an outer loop
then things become more complicated (you then could multiply by
max_loop_iterations of the containing loop maybe - but start simple ;))

  parent reply	other threads:[~2023-12-06  8:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03  9:14 [Bug tree-optimization/106511] New: [13 " marxin at gcc dot gnu.org
2022-08-03  9:14 ` [Bug tree-optimization/106511] " marxin at gcc dot gnu.org
2022-08-04  9:17 ` rguenth at gcc dot gnu.org
2022-12-20 14:39 ` rguenth at gcc dot gnu.org
2023-03-29 13:10 ` rguenth at gcc dot gnu.org
2023-04-08 14:42 ` law at gcc dot gnu.org
2023-04-26  6:56 ` [Bug tree-optimization/106511] [13/14 " rguenth at gcc dot gnu.org
2023-07-27  9:23 ` rguenth at gcc dot gnu.org
2023-11-06 21:38 ` amacleod at redhat dot com
2023-11-07 19:18 ` amacleod at redhat dot com
2023-12-06  8:55 ` rguenth at gcc dot gnu.org [this message]
2024-05-21  9:12 ` [Bug tree-optimization/106511] [13/14/15 " jakub 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-106511-4-s6iJ7jgBYn@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).