From: Jeff Law <law@redhat.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [RFA][PATCH] Use SCEV conditionally within vr-values and evrp range analysis
Date: Thu, 23 Nov 2017 15:32:00 -0000 [thread overview]
Message-ID: <2d549a96-e577-37ea-3c8d-526306bca941@redhat.com> (raw)
In-Reply-To: <CAFiYyc0yJOxpbuGRkrsnLvKjAC+QCDMq1zsfUOVk7szsqW5Kyg@mail.gmail.com>
On 11/23/2017 05:49 AM, Richard Biener wrote:
> On Thu, Nov 23, 2017 at 1:16 AM, Jeff Law <law@redhat.com> wrote:
>>
>> Clients of the evrp range analysis may not have initialized the SCEV
>> infrastructure, and in fact my not want to (DOM for example).
>>
>> Yet inside both vr-values.c and gimple-ssa-evrp-analyze.c we have calls
>> into SCEV (that will fault/abort if SCEV is not properly initialized).
>>
>> This patch allows clients of vr-values.c and gimple-ssa-evrp-analyze.c
>> to indicate if they want SCEV analysis.
>>
>> Bootstrapped and regression tested by itself as well as with the DOM
>> patches to use EVRP analysis (which test the "don't want SCEV path).
>>
>> OK for the trunk?
>
> There's also scev_initialized_p () which you could conveniently use.
Wasn't aware of it. That's almost certainly a better solution.
Jeff
next prev parent reply other threads:[~2017-11-23 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 8:13 Jeff Law
2017-11-23 13:14 ` Richard Biener
2017-11-23 15:32 ` Jeff Law [this message]
2017-11-27 16:58 ` [RFA][PATCH] Use SCEV conditionally within vr-values and evrp range analysis - V2 Jeff Law
2017-11-28 11:55 ` Richard Biener
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=2d549a96-e577-37ea-3c8d-526306bca941@redhat.com \
--to=law@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).