public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Abdul Wahid Memon <engrwahidmemon@gmail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Need info on GIMPLE
Date: Tue, 07 Jun 2011 22:34:00 -0000	[thread overview]
Message-ID: <BANLkTi=wD6tanXyPKqY5_9rpkwodivfWhQ@mail.gmail.com> (raw)
In-Reply-To: <mcraadtfm7w.fsf@coign.corp.google.com>

Does that mean that I have to traverse the control flow graph in order
to capture labels (if there are any) too.

Lets suppose if I want to count the number of gimple statements within
the body of the loop, then definitely I need the reference of that
target label for any conditional goto statement.

Regards

Abdul

On Tue, Jun 7, 2011 at 9:57 PM, Ian Lance Taylor <iant@google.com> wrote:
> Abdul Wahid Memon <engrwahidmemon@gmail.com> writes:
>
>> By the way, if I want to traverse through all the GIMPLE statements,
>> then from where should I start? I mean what should be the reference
>> point to capture those labels in the cfg.
>
> As far as I know, the way you were traversing GIMPLE was fine.  The
> labels you see in the dump, from the CFG, are not GIMPLE statements.
> They are basic_block structs connected by edge structs.
>
> Ian
>

  reply	other threads:[~2011-06-07 20:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30  6:09 Abdul Wahid Memon
2011-05-31  6:37 ` Ian Lance Taylor
2011-06-07 18:40   ` Abdul Wahid Memon
2011-06-07 19:38     ` Ian Lance Taylor
     [not found]       ` <BANLkTi=NGfc9p8LVO+0kv5kzt_RorQPTdQ@mail.gmail.com>
     [not found]         ` <mcrei35fmlc.fsf@coign.corp.google.com>
2011-06-07 20:09           ` Abdul Wahid Memon
2011-06-07 20:15             ` Ian Lance Taylor
2011-06-07 22:34               ` Abdul Wahid Memon [this message]
2011-06-07 22:54                 ` Ian Lance Taylor

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='BANLkTi=wD6tanXyPKqY5_9rpkwodivfWhQ@mail.gmail.com' \
    --to=engrwahidmemon@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=iant@google.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).