This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA/stabs reader] Fix v3 duplicate constructors problem
- From: Daniel Berlin <dan at cgsoftware dot com>
- To: Daniel Jacobowitz <drow at mvista dot com>
- Cc: <gdb-patches at sources dot redhat dot com>, <libstdc++ at gcc dot gnu dot org>
- Date: Mon, 3 Dec 2001 16:27:56 -0500 (EST)
- Subject: Re: [RFA/stabs reader] Fix v3 duplicate constructors problem
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