public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tom.horsley@ccur.com
To: gcc-gnats@gcc.gnu.org
Subject: debug/8094: bad dwarf for inlined constructors
Date: Mon, 30 Sep 2002 05:36:00 -0000 [thread overview]
Message-ID: <20020930123403.32505.qmail@sources.redhat.com> (raw)
>Number: 8094
>Category: debug
>Synopsis: bad dwarf for inlined constructors
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Sep 30 05:36:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: tom.horsley@ccur.com
>Release: gcc-3.2
>Organization:
>Environment:
redhat linux null beta release
>Description:
Apparently for some kind of multiple inheritance "optimization" g++ generates two separate copies of a constructor even when there is only one in the source and no inline was specified.
It creates debug info for both these constructors as though they were inlined, with two concrete instances and one abstract instance.
The concrete DIEs are all supposed to have DW_AT_abstract_origin attributes, pointing to the corresponding DIE in the abstract instance.
The dwarf generated by gcc 3.2 is missing the abstract
origin information for some DIEs in the concrete instance.
Specifically DW_TAG_lexical_block DIEs never seem to have
any abstract origin specified.
>How-To-Repeat:
I'm not sure when g++ decides to duplicate constructors like this, but if you can get it to do that, simply make the constructor big an complex enough to have inner lexical blocks, and you will see they never have abstract origin info.
P.S. Why it duplicates the entire constructor (which can be arbitrarily gigantic) instead of simply providing some little wrappers to do the vtable work is probably a subject for a different bug report :-).
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-09-30 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 5:36 tom.horsley [this message]
2002-10-17 14:33 dberlin
2003-02-23 21:26 neroden
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=20020930123403.32505.qmail@sources.redhat.com \
--to=tom.horsley@ccur.com \
--cc=gcc-gnats@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).