From: Martin Jambor <mjambor@suse.cz>
To: Gary Oblock <goblock@marvell.com>, GCC Development <gcc@gcc.gnu.org>
Subject: Re: How does one traverse all the global decls
Date: Thu, 22 Aug 2019 09:16:00 -0000 [thread overview]
Message-ID: <ri6lfvlef0p.fsf@suse.cz> (raw)
In-Reply-To: <MWHPR18MB107223C7CA8DAAF638C3F980B9AA0@MWHPR18MB1072.namprd18.prod.outlook.com>
Hi,
On Wed, Aug 21 2019, Gary Oblock wrote:
> I'm trying to do some analysis code for an optimization
> that involves my code looking at all the declarations and
> types there of during the link time optimizations.
>
> Note, doing this for the local variables seems to be trivial
> because of FOR_EACH_LOCAL_DECL and there are also
> obvious ways of getting at the type information once I have
> a decl. However, I can't seem to find any similar way of
> getting at the global level decls.
>
> I'd appreciate your help on this.
>
Look at FOR_EACH_VARIABLE defined in cgraph.h (because symtab.h does not
exist) and it's various uses throughout the compiler.
Martin
next prev parent reply other threads:[~2019-08-22 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 21:33 Gary Oblock
2019-08-22 9:16 ` Martin Jambor [this message]
2019-08-22 10:49 ` Richard Biener
2019-08-22 18:19 ` [EXT] " Gary Oblock
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=ri6lfvlef0p.fsf@suse.cz \
--to=mjambor@suse.cz \
--cc=gcc@gcc.gnu.org \
--cc=goblock@marvell.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).