From: Yuri Kashnikoff <yuri.kashnikoff@gmail.com>
To: Joern Rennecke <joern.rennecke@embecosm.com>
Cc: Li Feng <nemokingdom@gmail.com>,
Graphite <gcc-graphite@googlegroups.com>, GCC <gcc@gcc.gnu.org>
Subject: Re: Escape the unnecessary re-optimization in automatic parallelization.
Date: Tue, 13 Oct 2009 13:27:00 -0000 [thread overview]
Message-ID: <aa01cd760910130551k44ae457ax8e6083e52a3c7f24@mail.gmail.com> (raw)
In-Reply-To: <20091010052758.5rlaohiv440w84w8-nzlynne@webmail.spamcop.net>
> Therefore, the most effective way to address the issue of running redundant
> optimization passes in the context is probably to put it in the wider
> context
> of the work to allow external plugins to influence the pass sequence that is
> being applied, and to control this with machine learning.
>
Joern is right about external plugins. AFAIK, this work was done as a
part of GSoC#2009 project leaded by Grigori Fursin. Please check these
links for fufther information -
1) http://ctuning.org/wiki/index.php/CTools:ICI:Projects:GSOC09:Function_cloning_and_program_instrumentation#Work_with_adapt_plugin
2) http://ctuning.org/wiki/index.php/CTools:ICI:Projects:GSOC09:Scripts
In my opinion, you can easily edit XML's generated by adapt plugin to
exclude particular passes, then run scripts to make adapt plugin
substitute passes according to your edited XML files.
Thanks!
next prev parent reply other threads:[~2009-10-13 12:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 9:16 Li Feng
2009-10-10 10:55 ` Joern Rennecke
2009-10-11 16:05 ` Li Feng
2009-10-13 13:27 ` Yuri Kashnikoff [this message]
2009-10-14 6:23 ` Alexey Salmin
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=aa01cd760910130551k44ae457ax8e6083e52a3c7f24@mail.gmail.com \
--to=yuri.kashnikoff@gmail.com \
--cc=gcc-graphite@googlegroups.com \
--cc=gcc@gcc.gnu.org \
--cc=joern.rennecke@embecosm.com \
--cc=nemokingdom@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).