From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Michele Co <mc2zk@virginia.edu>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Any way to output information on compiler-generated temporary variables in gcc?
Date: Mon, 20 Jan 2014 15:55:00 -0000 [thread overview]
Message-ID: <CAH6eHdQc5nZ8+k3ksmBgbuPmPZ2Oen7d-e_fKDWfMpN=L=aq-g@mail.gmail.com> (raw)
In-Reply-To: <52DD39FD.80708@virginia.edu>
On 20 January 2014 15:00, Michele Co <mc2zk@virginia.edu> wrote:
> Hello,
>
> I'd like to gather/output information (size, offset, type -- if possible) of
> compiler-generated temporaries generated by gcc during compilation. I have
> looked through the compiler options related to generating debug information
> but am unsure whether there is an option available that will already give me
> this information in some form.
>
> Does anyone on this list know of a quick and relatively straightforward
> method for gathering and outputting this information if it hasn't already
> been done before?
One of the -fdump-tree-xxx options might provide the information you
want, e.g. -fdump-tree-original
I don't think debug info includes temporaries that aren't named in the
source, but I could be wrong.
next prev parent reply other threads:[~2014-01-20 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 14:49 Michele Co
2014-01-20 15:55 ` Jonathan Wakely [this message]
2014-01-22 19:36 ` Michele Co
2014-01-22 19:47 ` Jonathan Wakely
2014-01-23 16:37 ` Michele Co
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='CAH6eHdQc5nZ8+k3ksmBgbuPmPZ2Oen7d-e_fKDWfMpN=L=aq-g@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=mc2zk@virginia.edu \
/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).