public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Andrew MacLeod <amacleod@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
	Richard Biener <richard.guenther@gmail.com>,
	"hernandez, aldy" <aldyh@redhat.com>
Subject: Re: recomputation and PR 109154
Date: Thu, 30 Mar 2023 18:05:59 +0200	[thread overview]
Message-ID: <ZCWzZymjsVYfwo/q@tucnak> (raw)
In-Reply-To: <b3ae545e-661c-5988-2c26-00a9a4beae39@redhat.com>

On Thu, Mar 30, 2023 at 11:58:19AM -0400, Andrew MacLeod wrote:
> 
> On 3/30/23 09:41, Jakub Jelinek wrote:
> > On Wed, Mar 29, 2023 at 01:22:27PM -0400, Andrew MacLeod wrote:
> > > however, as seems to be the case often, better ranges result in, I now get:
> > > 
> > > FAIL: 23_containers/vector/bool/allocator/copy.cc (test for excess errors)
> > Our middle-end warnings are just badly designed :(, the better value ranges
> > are, the more false positives they have.
> > 
> > > commit 358d0ca44faf2e20fbacd0f74386308b5ca52cd4
> > > Author: Andrew MacLeod <amacleod@redhat.com>
> > > Date:   Tue Mar 28 12:16:34 2023 -0400
> > > 
> > >      Add recursive GORI recompuations with a depth limit.
> > LGTM for trunk, let's do with the regression incrementally.
> > Or as Richard mentioned on IRC, one possibility would be to force this
> > param temporarily to 1 (or whatever matches previous behavior) for the
> > diagnostic range queries).
> > 
> > You need a ChangeLog entry though...
> > 
> Attached. I also removed the bogus warning in Walloc-13.c that no longer
> happens
> 
> So incrementally deal with it.. what? just let it fail?

For today?  Yes.

Ok for trunk.

> commit debb8ce1f9b9d5a72d88d0ae90a6b4da5130ff59
> Author: Andrew MacLeod <amacleod@redhat.com>
> Date:   Tue Mar 28 12:16:34 2023 -0400
> 
>     Add recursive GORI recompuations with a depth limit.
>     
>             PR tree-optimization/109154
>             gcc/
>             * gimple-range-gori.cc (gori_compute::may_recompute_p): Add depth limit.
>             * gimple-range-gori.h (may_recompute_p): Add depth param.
>             * params.opt (ranger-recompute-depth): New param.
>     
>             gcc/testsuite/
>             * gcc.dg/Walloca-13.c: Remove bogus warning that is now fixed.

	Jakub


  reply	other threads:[~2023-03-30 16:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 17:22 Andrew MacLeod
2023-03-30  6:42 ` Richard Biener
2023-03-30 13:41 ` Jakub Jelinek
2023-03-30 15:58   ` Andrew MacLeod
2023-03-30 16:05     ` Jakub Jelinek [this message]
2023-03-30 20:39       ` Andrew MacLeod
2023-03-31  6:08         ` Andrew Pinski
2023-03-31 16:12     ` Regression with "recomputation and PR 109154" Hans-Peter Nilsson
2023-03-31 16:20       ` Jeff Law
2023-03-31 17:02         ` Andrew MacLeod
2023-03-31 17:37           ` Jakub Jelinek
2023-03-31 19:48             ` Andrew MacLeod
2023-03-31 19:59               ` Jeff Law
2023-03-31 20:16                 ` Andrew MacLeod
2023-03-31 20:20                   ` Jeff Law
2023-03-31 23:31               ` Hans-Peter Nilsson
2023-04-01  1:11                 ` Andrew MacLeod

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=ZCWzZymjsVYfwo/q@tucnak \
    --to=jakub@redhat.com \
    --cc=aldyh@redhat.com \
    --cc=amacleod@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    /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).