From: Andrew Cagney <cagney@redhat.com>
To: Sami Wagiaalla <swagiaal@redhat.com>, frysk <frysk@sourceware.org>
Subject: frame->function
Date: Mon, 07 May 2007 21:32:00 -0000 [thread overview]
Message-ID: <463F8191.1000903@redhat.com> (raw)
Sami,
Just FYI, here's an ASCII version of the frame/function relationship
diagram:
.---FRAME--1:N--FUNCTION--1:N--BLOCK--1:N--VARIABLE
| | \ | \
`----' \ | 1:N
1:N | \
\ | `PARAMETER
\ |
FILE/LINE/COL
that is:
- an ABI stack frame has inner/outer FRAME
- an ABI stack frame, has one-or-more source function/method associated
with it - more than one due too inlining
- A "function" has one or more "block scopes" associated with it
- A block-scope than has one or more variables associated with it
and: A frame as one-or-more FILE/LINE/COL's due to inlining ;; and the
FUNCTION will also point into that same info - so that one can tell
which function a file
Andrew
next reply other threads:[~2007-05-07 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 21:32 Andrew Cagney [this message]
2007-05-09 15:06 ` frame->function Stan Cox
2007-05-09 18:01 ` frame->function Sami Wagiaalla
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=463F8191.1000903@redhat.com \
--to=cagney@redhat.com \
--cc=frysk@sourceware.org \
--cc=swagiaal@redhat.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).