From: Richard Biener <rguenther@suse.de>
To: Andrew MacLeod <amacleod@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>, Jan Hubicka <jh@suse.cz>,
Aldy Hernandez <aldyh@redhat.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] middle-end IFN_ASSUME support [PR106654]
Date: Thu, 13 Oct 2022 08:11:53 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2210130810040.18337@jbgna.fhfr.qr> (raw)
In-Reply-To: <94879a41-16b5-6ec4-51ab-4d931b608147@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3113 bytes --]
On Wed, 12 Oct 2022, Andrew MacLeod wrote:
>
> On 10/12/22 10:39, Jakub Jelinek wrote:
> > On Wed, Oct 12, 2022 at 10:31:00AM -0400, Andrew MacLeod wrote:
> >> I presume you are looking to get this working for this release, making the
> >> priority high? :-)
> > Yes. So that we can claim we actually support C++23 Portable Assumptions
> > and OpenMP assume directive's hold clauses for something non-trivial so
> > people won't be afraid to actually use it.
> > Of course, first the posted patch needs to be reviewed and only once it gets
> > in, the ranger/GORI part can follow. As the latter is only an optimization,
> > it can be done incrementally.
>
> I will start poking at something to find ranges for parameters from the return
> backwards.
If the return were
if (return_val)
return return_val;
you could use path-ranger with the parameter SSA default defs as
"interesting". So you "only" need to somehow interpret the return
statement as such and do path rangers compute_ranges ()
>
> >> Intersection I believe...? I think the value from the assume's should add
> >> restrictions to the range..
> > Sure, sorry.
> >
> >> I figured as much, I was just wondering if there might be some way to
> >> "simplify" certain things by processing it and turning each parameter query
> >> into a smaller function returning the range we determined from the main
> >> one... but perhaps that is more complicated.
> > We don't really know what the condition is, it can be pretty arbitrary
> > expression (well, e.g. for C++ conditional expression, so say
> > [[assume (var = foo ())]];
> > is not valid but
> > [[assume ((var = foo ()))]];
> > is. And with GNU statement expressions it can do a lot of stuff and until
> > we e.g. inline into it and optimize it a little, we don't really know what
> > it will be like.
> >
> >
>
> No, I just meant that once we finally process the complicated function, and
> decide the final range we are storing is for x_1 is say [20,30], we could
> replace the assume call site with something like
>
> int assume03_x (x) { if (x>= 20 || x <= 30) return x; gcc_unreachable(); }
>
> then at call sites:
>
> x_5 = assume03_x(x_3);
>
> For that matter, once all the assume functions have been processed, we could
> textually replace the assume call with an expression which represents the
> determined range... Kind of our own mini inlining? Maybe thats even better
> than adding any kind of support in fold_using_range.. just let things
> naturally fall into place?
>
> .ASSUME_blah ( , , x_4);
>
> where if x is determined to be [20, 30][50,60] could be textually "expanded"
> in the IL with
>
> if (x<20 || x>60 || (x>30 && x < 50)) gcc_unreachcable();
>
> for each of the parameters? If we processed this like early inlining, we
> could maybe expose the entire thing to optimization that way?
>
> Andrew
>
>
>
--
Richard Biener <rguenther@suse.de>
SUSE Software Solutions Germany GmbH, Frankenstrasse 146, 90461 Nuernberg,
Germany; GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman;
HRB 36809 (AG Nuernberg)
next prev parent reply other threads:[~2022-10-13 8:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 8:54 Jakub Jelinek
2022-10-10 21:09 ` Jason Merrill
2022-10-10 21:19 ` Jakub Jelinek
2022-10-11 13:36 ` [PATCH] middle-end, v2: " Jakub Jelinek
2022-10-12 15:48 ` Jason Merrill
2022-10-13 6:50 ` [PATCH] middle-end, v3: " Jakub Jelinek
2022-10-14 11:27 ` Richard Biener
2022-10-14 18:33 ` Jakub Jelinek
2022-10-17 6:55 ` Richard Biener
2022-10-17 15:44 ` [PATCH] middle-end, v4: " Jakub Jelinek
2022-10-18 7:00 ` Richard Biener
2022-10-18 21:31 ` Andrew MacLeod
2022-10-19 16:06 ` Jakub Jelinek
2022-10-19 16:55 ` Andrew MacLeod
2022-10-19 17:39 ` Jakub Jelinek
2022-10-19 17:41 ` Jakub Jelinek
2022-10-19 18:25 ` Andrew MacLeod
2022-10-19 17:14 ` Andrew MacLeod
2022-10-11 18:05 ` [PATCH] middle-end " Andrew MacLeod
2022-10-12 10:15 ` Jakub Jelinek
2022-10-12 14:31 ` Andrew MacLeod
2022-10-12 14:39 ` Jakub Jelinek
2022-10-12 16:12 ` Andrew MacLeod
2022-10-13 8:11 ` Richard Biener [this message]
2022-10-13 9:53 ` Jakub Jelinek
2022-10-13 13:16 ` Andrew MacLeod
2022-10-13 9:57 ` Jakub Jelinek
2022-10-17 17:53 ` Andrew MacLeod
2022-10-14 20:43 ` Martin Uecker
2022-10-14 21:20 ` Jakub Jelinek
2022-10-15 8:07 ` Martin Uecker
2022-10-15 8:53 ` Jakub Jelinek
2022-10-17 5:52 ` Martin Uecker
2022-11-08 9:19 Pilar Latiesa
2022-11-08 12:10 ` Jakub Jelinek
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=nycvar.YFH.7.77.849.2210130810040.18337@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=aldyh@redhat.com \
--cc=amacleod@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jh@suse.cz \
/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).