From: Tobias Grosser <grosser@fim.uni-passau.de>
To: sandeep soni <saintiwara@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: loop optimization in gcc
Date: Tue, 13 Oct 2009 09:42:00 -0000 [thread overview]
Message-ID: <1255415925.3362.4.camel@tobilaptop> (raw)
In-Reply-To: <43e4d4d20910110750v26711f80w793a5da15b267ff2@mail.gmail.com>
On Sun, 2009-10-11 at 20:20 +0530, sandeep soni wrote:
> Hi All,
>
> I have been studying the gcc code lately as part of my project.I have
> got info from this mailing list about CFG and DFG information.I want
> to know how gcc uses this information to perform loop optimization?
> Does it Follow any particular algorithm or in particular what are the
> different techniques that it uses to parallelize the code by
> performing the loop optimizations?(correct me please if this sentence
> is not right).
>
> If possible please provide any pointers to any form of literature
> available regarding it.
>
> Thanks in advance.
Hi,
you also might want to take a look at the Graphite project.
http://gcc.gnu.org/wiki/Graphite where we do loop optimizations and
automatic parallelization based on the polytop model. If you need any
help feel free to ask.
Tobias
next prev parent reply other threads:[~2009-10-13 6:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-11 15:21 sandeep soni
2009-10-12 8:53 ` Ian Lance Taylor
2009-10-12 17:58 ` sandeep soni
2009-10-12 18:03 ` Ian Lance Taylor
2009-10-12 21:15 ` sandeep soni
2009-10-13 9:42 ` Tobias Grosser [this message]
2009-10-14 15:32 ` sandeep soni
[not found] ` <25720_1255531382_4AD5E376_25720_275_1_43e4d4d20910140742l5e4f60ebidfcfe72ff9f6db65@mail.gmail.com>
2009-10-14 15:42 ` Tobias Grosser
2009-10-14 18:29 ` sandeep soni
[not found] ` <3215_1255544820_4AD617F4_3215_317_1_43e4d4d20910141126j687a89b6wf619416c604e085b@mail.gmail.com>
2009-10-15 7:46 ` Tobias Grosser
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=1255415925.3362.4.camel@tobilaptop \
--to=grosser@fim.uni-passau.de \
--cc=gcc@gcc.gnu.org \
--cc=saintiwara@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).