public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: <Primrose.Mbanefo@Infineon.com>
To: <gcc-help@gcc.gnu.org>
Subject: Question on accessing and using binfos
Date: Tue, 02 Aug 2005 16:14:00 -0000	[thread overview]
Message-ID: <BBBAD038CF62944F8BC0E9B2351EC52201115E69@mucse205.eu.infineon.com> (raw)

Hello,

I'm wondering if I can get information from here on how to use the binfo
macros.

These two macros, BINFO_BASE_BINFO and BINFO_BASE_ITERATE, are mentioned
on the onlinedocs webpage but I can't find any header file describing
them which means the compilation always fails.
Are they still current? Or should I use something else instead? (I have
gcc 3.4.1)

How should these macros be used? If class A is mother class to B with
the assosciated trees being Atree and Btree repectively, does
TYPE_BINFO(Btree) give Atree?
Or should BINFO_BASE_BINFO(TYPE_BINFO(Btree)) give Atree?
And what does BINFO_TYPE actually do? (sorry but I don't really
understand the instructions on the webpage...)

I would also like information on accessing trees from their types.
A library acting as backend to GCC gives me access to a class C's tree,
let's say Ctree.
I would like to know if C is derived from D. normally I should do,
same_type-p(Ctree, Dtree) {I guess...}
but I don't have or don't know how to get the Dtree. I just know that
the name of the class is D.
Is there a macro for retrieving the tree representing a class from its
name or any known way of doing such a thing?

Thanks for any answers.

Primrose

             reply	other threads:[~2005-08-02 16:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02 16:14 Primrose.Mbanefo [this message]
2005-08-02 18:26 ` 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=BBBAD038CF62944F8BC0E9B2351EC52201115E69@mucse205.eu.infineon.com \
    --to=primrose.mbanefo@infineon.com \
    --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).