public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drow at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/14168] New: Unneeded DIEs output for imported declarations
Date: Tue, 17 Feb 2004 04:54:00 -0000	[thread overview]
Message-ID: <20040217045409.14168.drow@gcc.gnu.org> (raw)

This code:
typedef int ptrdiff_t;

namespace std
{
  using ::ptrdiff_t;
}

causes DIEs to be output for ptrdiff_t, std, std::ptrdiff_t, and int.  None of these
are necessary.  Ideally DW_TAG_imported_declaration would be pruned if !TREE_USED;
we have no way to find out if the copy in std is used or not.

This example highlights how schizophrenic we are about when to emit things.  We
go out of our way to emit as little as possible (way too little) for some things,
but anything imported into anything else is output, and it's not clear what use
DW_TAG_imported_declaration has if we don't do that.  There are imports all over
the standard headers and this causes lots of wasted duplicate DIEs.

-- 
           Summary: Unneeded DIEs output for imported declarations
           Product: gcc
           Version: 3.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: debug
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: drow at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14168


             reply	other threads:[~2004-02-17  4:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-17  4:54 drow at gcc dot gnu dot org [this message]
2004-02-17  5:06 ` [Bug debug/14168] " pinskia at gcc dot gnu dot org
2004-06-06 18:16 ` dberlin at gcc dot gnu dot org

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=20040217045409.14168.drow@gcc.gnu.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).