From: Jeff Law <jeffreyalaw@gmail.com>
To: Hans-Peter Nilsson <hp@axis.com>, Andrew MacLeod <amacleod@redhat.com>
Cc: jakub@redhat.com, gcc-patches@gcc.gnu.org,
richard.guenther@gmail.com, aldyh@redhat.com
Subject: Re: Regression with "recomputation and PR 109154"
Date: Fri, 31 Mar 2023 10:20:23 -0600 [thread overview]
Message-ID: <5c5825b2-c4f0-8aa7-c324-8256829e52f5@gmail.com> (raw)
In-Reply-To: <20230331161207.DB49620444@pchp3.se.axis.com>
On 3/31/23 10:12, Hans-Peter Nilsson via Gcc-patches wrote:
>> Attached. I also removed the bogus warning in Walloc-13.c that no longer
>> happens
>
>> 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.
>
> This patch, commit r13-6945-g429a7a88438cc8, caused a
> test-suite regression; FAIL for 'gcc.dg/tree-ssa/pr23109.c
> scan-tree-dump-not recip "reciptmp"' for cris-elf that I
> logged at PR109363.
>
> Perhaps it's somewhat of a similar nature as Walloca-13.c
> but then again it's not an bogus warning that's gone.
>
> Is it expected and I should just blankly xfail it or is it
> worth more attention? I'm a bit surprised that it hasn't
> shown up for other targets though.
I already let Andrew know -- it's affecting a ton of targets. It may be
the case that we just need to adjust the param for that test.
jeff
next prev parent reply other threads:[~2023-03-31 16:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 17:22 recomputation and PR 109154 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
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 [this message]
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=5c5825b2-c4f0-8aa7-c324-8256829e52f5@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=aldyh@redhat.com \
--cc=amacleod@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@axis.com \
--cc=jakub@redhat.com \
--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).