From: Daniel Berlin <dberlin@dberlin.org>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb-patches@sources.redhat.com,
Elena Zannoni <ezannoni@redhat.com>, Jim Blandy <jimb@redhat.com>
Subject: Re: [rfc/rfa] accept DW_TAG_namespace and friends, possibly on 5.3
Date: Tue, 22 Oct 2002 15:09:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0210221726360.14211-100000@dberlin.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0210221710400.10022-100000@dberlin.org>
> > currently have a version of GCC that emits many
> > DW_TAG_imported_declarations or any DW_TAG_imported_modules; I hope
> > that I'll have one soon (Daniel Berlin is working on it but he's busy;
> > maybe I'll try to work on it myself, too),
> I should have it done in a few hours, actually.
Now I remember why i didn't do it in the first place.
Using decl's aren't common to the tree structure (USING_DECL and
USING_STMT are in cp/cp-tree.def).
We also never end up walking the statement tree, and there are no debug
hooks
for handling each statement anyway (inlined subroutines get handled
without needing to do this), so it's a loss.
Thus, we'll never see a USING_STMT or USING_DECL.
In other words, this is gonna be complicated and i don't know if it'll be
accepted, but we'll see.
I can make the DW_TAG_imported_* appear and appear in the right order, but
not necessarily in the right context.
--Dan
next prev parent reply other threads:[~2002-10-22 22:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 13:40 David Carlton
2002-10-22 13:51 ` Daniel Jacobowitz
2002-10-22 14:25 ` Andrew Cagney
2002-10-22 14:17 ` Daniel Berlin
2002-10-22 14:40 ` David Carlton
2002-10-22 15:09 ` Daniel Berlin [this message]
2002-10-22 15:33 ` David Carlton
2002-10-22 16:48 ` Daniel Berlin
2002-10-22 15:29 ` Elena Zannoni
2002-10-22 16:02 ` David Carlton
2002-10-22 16:10 ` Elena Zannoni
2002-10-22 16:14 ` David Carlton
2002-10-23 11:36 ` David Carlton
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=Pine.LNX.4.44.0210221726360.14211-100000@dberlin.org \
--to=dberlin@dberlin.org \
--cc=carlton@math.stanford.edu \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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