public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Iyer, Balaji V" <balaji.v.iyer@intel.com>
To: Ian Lance Taylor <iant@google.com>
Cc: "'gcc@gcc.gnu.org'" <gcc@gcc.gnu.org>
Subject: RE: Function Name from CALL_INSN RTX
Date: Tue, 18 Oct 2011 15:00:00 -0000	[thread overview]
Message-ID: <2950715866004049A240A2F9BB410E7315FB28F60A@azsmsx502.amr.corp.intel.com> (raw)
In-Reply-To: <mcrehya7vnt.fsf@coign.corp.google.com>

Thanks for the help Ian. The function get_callee_fndecl takes in a tree and returns a tree. I would like to get the function name from the RTX. Is there a function for this purpose? 

Thanks,

Balaji V. Iyer.


________________________________________
From: Ian Lance Taylor [iant@google.com]
Sent: Tuesday, October 18, 2011 12:47 AM
To: Iyer, Balaji V
Cc: 'gcc@gcc.gnu.org'
Subject: Re: Function Name from CALL_INSN RTX

"Iyer, Balaji V" <balaji.v.iyer@intel.com> writes:

>        Is it possible to extract the function name (as a tree or char *)  from a CALL_INSN RTX? Is there a #define or a series of #defines that can accomplish this?

Not always, of course.  A call through a function pointer has no name.

The function get_callee_fndecl will do its best to get the function decl
from a CALL_EXPR.

Ian

  reply	other threads:[~2011-10-18 13:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18  8:21 Iyer, Balaji V
2011-10-18  8:23 ` Ian Lance Taylor
2011-10-18 15:00   ` Iyer, Balaji V [this message]
2011-10-18 15:12     ` 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=2950715866004049A240A2F9BB410E7315FB28F60A@azsmsx502.amr.corp.intel.com \
    --to=balaji.v.iyer@intel.com \
    --cc=gcc@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).