From: Sebastian Pop <sebpop@gmail.com>
To: Tom de Vries <Tom_deVries@mentor.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
Thomas Schwinge <thomas@codesourcery.com>,
"gcc-patches@gnu.org" <gcc-patches@gnu.org>
Subject: Re: [RFC, PR66873] Use graphite for parloops
Date: Mon, 20 Jul 2015 18:53:00 -0000 [thread overview]
Message-ID: <20150720182239.GA20717@f1.c.bardezibar.internal> (raw)
In-Reply-To: <55A7935A.60401@mentor.com>
Tom de Vries wrote:
> >>>graphite dependence analysis is too slow to be enabled unconditionally.
> >>>(read: hours in some simple cases - see bugzilla)
> >>
> >>Haha, "cool"! ;-)
> >>
> >>Maybe it is still reasonable to use graphite to analyze the code inside
> >>OpenACC kernels regions -- maybe such code can reasonably be expected to
> >>not have the properties that make its analysis lengthy? So, Tom, could
> >>you please identify and check such PRs, to get an understanding of what
> >>these properties are?
> >
> >Like the one in PR62113 or 53852 or 59121.
>
> PR62113 and PR59121 do not reproduce for me on trunk.
>
> PR53852 does reproduce for me (to the point that I had to reset my laptop).
ISL has a way to count the number of operations, based on a watermark it will
output an error code that we can use to leave graphite: see documentation of
isl_ctx_set_max_operations(). With that mechanism we can set a goal for
graphite of at max (say 10% overhead) of whole compilation time.
next prev parent reply other threads:[~2015-07-20 18:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 22:18 Tom de Vries
2015-07-16 8:48 ` Richard Biener
2015-07-16 10:25 ` Thomas Schwinge
2015-07-16 10:28 ` Richard Biener
2015-07-16 10:41 ` Richard Biener
2015-07-26 22:54 ` Tom de Vries
2015-07-27 5:41 ` Sebastian Pop
2015-07-16 11:41 ` Tom de Vries
2015-07-20 18:53 ` Sebastian Pop [this message]
2015-07-21 0:22 ` Tom de Vries
2015-07-20 18:54 ` Sebastian Pop
2015-07-21 5:59 ` Tom de Vries
2015-07-21 14:35 ` Tom de Vries
2015-07-21 19:08 ` Sebastian Pop
2015-07-22 11:02 ` Richard Biener
2015-07-22 11:18 ` Richard Biener
2015-07-22 16:04 ` [PATCH] Don't allow unsafe reductions in graphite Tom de Vries
2015-07-23 10:51 ` Richard Biener
2015-07-24 20:37 ` Sebastian Pop
2015-07-25 11:41 ` Tom de Vries
2015-07-22 16:38 ` [PATCH] Check TYPE_OVERFLOW_WRAPS for parloops reductions Tom de Vries
2015-07-23 10:54 ` Richard Biener
2015-07-24 10:43 ` [committed] Remove xfail in autopar/uns-outer-4.c Tom de Vries
2015-07-24 11:54 ` [PATCH] Add FIXED_POINT_TYPE_OVERFLOW_WRAPS_P Tom de Vries
2015-07-22 15:33 ` [PATCH] Document ftrapv/fwrapv interaction Tom de Vries
2015-07-23 10:39 ` Richard Biener
2015-07-23 10:42 ` 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=20150720182239.GA20717@f1.c.bardezibar.internal \
--to=sebpop@gmail.com \
--cc=Tom_deVries@mentor.com \
--cc=gcc-patches@gnu.org \
--cc=richard.guenther@gmail.com \
--cc=thomas@codesourcery.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).