From: Daniel Berlin <dan@cgsoftware.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: <gdb-patches@sources.redhat.com>, <libstdc++@gcc.gnu.org>
Subject: Re: [RFA/stabs reader] Fix v3 duplicate constructors problem
Date: Mon, 03 Dec 2001 13:28:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0112031627090.20609-100000@www.cgsoftware.com> (raw)
In-Reply-To: <20011203162542.A597@nevyn.them.org>
On Mon, 3 Dec 2001, Daniel Jacobowitz wrote:
> On Mon, Dec 03, 2001 at 04:22:14PM -0500, Daniel Berlin wrote:
> >
> >
> > On Mon, 3 Dec 2001, Daniel Jacobowitz wrote:
> >
> > > I tracked down the annoying duplication of constructors using G++ 3.0 with
> > > stabs. The problem is that all the clones of the constructor are emitted,
> > > so there really are two of them.
> > >
> > Yes.
> > > The obvious thing to do to fix this in GCC (and I'd like it fixed in GCC)
> > > would seem to be checking DECL_ABSTRACT_ORIGIN like the Dwarf frontend does
> > > instead of DECL_ABSTRACT.
> > It *used* to do the right thing (IE after the v3 switch)
> > Which is to emit a single constructor name in the class, and emit the
> > clones outside the class debug info, with an abstract origin/specification
> > of the in the class die.
> >
> > Does it not still do this?
>
> It does for Dwarf2. This particular problem does not affect Dwarf2.
> Dies don't come into this anywhere.
Sorry, missed the part where you said it was with stabs.
--Dan
next prev parent reply other threads:[~2001-12-03 21:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 12:48 Daniel Jacobowitz
2001-12-03 13:22 ` Daniel Berlin
2001-12-03 13:25 ` Daniel Jacobowitz
2001-12-03 13:28 ` Daniel Berlin [this message]
2001-12-03 13:52 ` Jason Merrill
2001-12-03 14:29 ` Daniel Jacobowitz
2001-12-03 14:58 ` Jason Merrill
2001-12-03 15:25 ` Michael Snyder
2001-12-04 8:25 ` Jason Merrill
2001-12-04 8:53 ` Jim Blandy
2001-12-04 9:43 ` Joe Buck
2001-12-07 15:25 ` Jim Blandy
2001-12-07 15:30 ` Daniel Jacobowitz
2001-12-04 1:09 Michael Elizabeth Chastain
2001-12-04 5:27 ` Jason Merrill
2001-12-04 7:40 ` Daniel Berlin
2001-12-04 8:58 ` Daniel Jacobowitz
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.33.0112031627090.20609-100000@www.cgsoftware.com \
--to=dan@cgsoftware.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=libstdc++@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