public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: ranjith kumar <ranjit_kumar_b4u@yahoo.co.uk>
Cc: gcc-help@gcc.gnu.org
Subject: Re: printing "tree" type data
Date: Mon, 04 Jun 2007 23:19:00 -0000	[thread overview]
Message-ID: <m36463l36k.fsf@localhost.localdomain> (raw)
In-Reply-To: <20070604142104.22149.qmail@web27411.mail.ukl.yahoo.com>

ranjith kumar <ranjit_kumar_b4u@yahoo.co.uk> writes:

>     I want to print the last statement(which is of
> "tree" type) in a given basic block. 
> 
> The last statement of a basic-block pointed by bb can
> be get by last_stmt(bb);
> I want to see that instruction.
> 
> I want to print that statement to a dump file or
> standard output. Ordinary data types can be printed by
> fprintf in source code. But how to print "tree" data
> type?

Look at the debug_tree and debug_generic_stmt functions.

Look at gcc/gdbinit.in for some useful gdb macros.

Ian

      reply	other threads:[~2007-06-04 23:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-04 14:21 ranjith kumar
2007-06-04 23:19 ` Ian Lance Taylor [this message]

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=m36463l36k.fsf@localhost.localdomain \
    --to=iant@google.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=ranjit_kumar_b4u@yahoo.co.uk \
    /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).