From: Michele Co <mc2zk@virginia.edu>
To: gcc-help@gcc.gnu.org
Subject: Any way to output information on compiler-generated temporary variables in gcc?
Date: Mon, 20 Jan 2014 14:49:00 -0000 [thread overview]
Message-ID: <52DD39FD.80708@virginia.edu> (raw)
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?
Thanks!
Michele
next reply other threads:[~2014-01-20 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 14:49 Michele Co [this message]
2014-01-20 15:55 ` Jonathan Wakely
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=52DD39FD.80708@virginia.edu \
--to=mc2zk@virginia.edu \
--cc=gcc-help@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).