public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sandeep K Chaudhary <babbusandy2006@gmail.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>, gcc@gcc.gnu.org
Subject: Re: GIMPLE pass - Assignment evaluation
Date: Tue, 17 Dec 2013 06:24:00 -0000	[thread overview]
Message-ID: <CAEEAEzUJfFC50=e49UPD6xW-pSozrhCUv5HJaD4yKd=b9rfshg@mail.gmail.com> (raw)
In-Reply-To: <1387243963.25856.19.camel@surprise>

Thank you so much for the reply, David !

I am not sure where exactly my pass gets invoked. I will try to find it.
But the pass get invoked somewhere in the GIMPLE stage as shown in the
GCC architecture[1].
How is it that one can dictate where the pass can be invoked? Can you
please provide some pointers/links about this?

But looking at the GCC architecture[1], I can see that the
optimization passes come into picture only after GIMPLE and SSA stage.
 I dumped the IR and other related files using -fdump-tree-all with
optimization flag -O1, and saw that the assignments have not been
evaluated for test.c.004t.gimple as well as test.c.018t.ssa.

Also, in test.c.025t.forwprop1 and test.c.029t.copyprop1, they totally
get rid of everything in the assignments i.e. they only have the final
evaluation of the variables which is not what I want as I need
evaluation for individual statements.

[2] provides a nice diagrammatic understanding of the relative
invocations of GCC opt passes. It is quite helpful for understanding
the relative positions of the passes.

Thanks and regards,
Sandeep.

[1] http://en.wikibooks.org/wiki/GNU_C_Compiler_Internals/GNU_C_Compiler_Architecture
[2] https://gcc-python-plugin.readthedocs.org/en/latest/tables-of-passes.html

  reply	other threads:[~2013-12-17  6:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 21:10 Sandeep K Chaudhary
2013-12-17  1:33 ` David Malcolm
2013-12-17  6:24   ` Sandeep K Chaudhary [this message]
2013-12-17  6:41     ` Uday P. Khedker
2013-12-17  7:26       ` Sandeep K Chaudhary
  -- strict thread matches above, loose matches on Subject: below --
2013-12-09 23:05 Sandeep K Chaudhary
2013-07-02  3:24 Sandeep K Chaudhary
2013-07-02  5:44 ` Marc Glisse
2013-07-02 17:09   ` Sandeep K Chaudhary
2013-07-10  8:18     ` Sandeep K Chaudhary

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='CAEEAEzUJfFC50=e49UPD6xW-pSozrhCUv5HJaD4yKd=b9rfshg@mail.gmail.com' \
    --to=babbusandy2006@gmail.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    /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).