public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/16253] Cannot print an enum var with the same name as tag
Date: Wed, 03 Jun 2015 17:32:00 -0000	[thread overview]
Message-ID: <bug-16253-4717-4s1EwAmKXS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16253-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16253

--- Comment #15 from dje at google dot com ---
IWBN to look into whether a STRUCT/VAR_DOMAIN indicator can be added to the
index. The problem, I fear, will be getting gcc+gold to generate it.
[Which is an important problem to solve as the official DWARF index (in
DWARFv6?) may have the same problem ... and it's getting late in the day ... do
we need to make changes to the official index?]

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-06-03 17:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26 14:24 [Bug gdb/16253] New: " polacek at redhat dot com
2013-11-26 14:27 ` [Bug gdb/16253] " polacek at redhat dot com
2013-11-27 18:52 ` keiths at redhat dot com
2013-11-27 23:48 ` polacek at redhat dot com
2014-03-21 18:14 ` [Bug c++/16253] " keiths at redhat dot com
2014-04-14 22:56 ` cvs-commit at gcc dot gnu.org
2014-04-14 22:57 ` keiths at redhat dot com
2014-05-28  1:51 ` dje at google dot com
2014-05-28  1:54 ` dje at google dot com
2014-05-28 17:25 ` dje at google dot com
2014-06-04  3:32 ` xdje42 at gmail dot com
2014-08-29 13:37 ` lgustavo at codesourcery dot com
2015-06-03 15:36 ` fche at redhat dot com
2015-06-03 16:06 ` jason at redhat dot com
2015-06-03 16:09 ` jason at redhat dot com
2015-06-03 16:10 ` jason at redhat dot com
2015-06-03 16:15 ` dje at google dot com
2015-06-03 16:19 ` mgretton at sourceware dot org
2015-06-03 17:32 ` dje at google dot com [this message]
2015-06-04 16:01 ` fweimer at redhat dot com
2015-06-04 17:29 ` dje at google dot com
2015-06-12 15:53 ` keiths at redhat dot com
2015-06-26 18:43 ` cvs-commit at gcc dot gnu.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=bug-16253-4717-4s1EwAmKXS@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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).