From: "Iyer, Balaji V" <balaji.v.iyer@intel.com>
To: "'gcc@gcc.gnu.org'" <gcc@gcc.gnu.org>
Subject: Function Name from CALL_INSN RTX
Date: Tue, 18 Oct 2011 08:21:00 -0000 [thread overview]
Message-ID: <2950715866004049A240A2F9BB410E7315FB11509F@azsmsx502.amr.corp.intel.com> (raw)
Hello Everyone,
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?
The tried to find this information by stepping through the print_rtx function using gdb and the information (as a char *) is currently stored in the following location of a CALL_INSN: "insn->u.fld[4]->rt_rtx->u.fld[1]->rt_rtx->u.fld[0]->rt_rtx->u.fld[0]->rt_rtx->u.fld[0]->rt_str "
Does anyone know of a #define or a function I can call to retrieve this information? I would prefer to use functions or #defines rather than absolute locations for future compatibility.
Any help is greatly appreciated!
Thanks,
Balaji V. Iyer.
next reply other threads:[~2011-10-18 4:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 8:21 Iyer, Balaji V [this message]
2011-10-18 8:23 ` Ian Lance Taylor
2011-10-18 15:00 ` Iyer, Balaji V
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=2950715866004049A240A2F9BB410E7315FB11509F@azsmsx502.amr.corp.intel.com \
--to=balaji.v.iyer@intel.com \
--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).