public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Josh Stone <jistone@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: [PATCH] dwarf.h: Remove non-existing DW_TAG_mutable_type.
Date: Wed, 18 Jun 2014 08:48:20 -0700	[thread overview]
Message-ID: <53A1B4C4.8050205@redhat.com> (raw)
In-Reply-To: 1403084921-16852-1-git-send-email-mjw@redhat.com

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]

On 06/18/2014 02:48 AM, Mark Wielaard wrote:
> The DW_TAG_mutable_type was only mentioned in an early draft of DWARFv3.
> But was removed because there are no C++ mutable qualified types. It was
> replaced by a new attribute DW_AT_mutable on DW_TAG_member DIEs. The new
> attribute is available in dwarf.h.
> http://dwarfstd.org/ShowIssue.php?issue=050223.1
> 
> DW_TAG_mutable_type was only used internally in some backends (which
> just ignored it anyway). dwarves did use it to turn it into a string
> value, libabigail used it and ignored it (patches to remove sent).
> GCC, GDB and binutils don't use nor define it.

It's fine to patch its use out, in elfutils and others, but why take the
API hit of removing the constant?  The number is still allocated, so it
won't do any harm to leave it there.

For example, libdwarf just commented on the removal:
>         /*  Do not use DW_TAG_mutable_type */
> #define DW_TAG_mutable_type 0x3e /* Withdrawn from DWARF3 by DWARF3f. */



             reply	other threads:[~2014-06-18 15:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18 15:48 Josh Stone [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-06-22 17:31 Mark Wielaard
2014-06-19 10:03 Mark Wielaard
2014-06-18 21:35 Roland McGrath
2014-06-18 18:48 Josh Stone
2014-06-18 18:38 Mark Wielaard
2014-06-18  9:48 Mark Wielaard

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=53A1B4C4.8050205@redhat.com \
    --to=jistone@redhat.com \
    --cc=elfutils-devel@lists.fedorahosted.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).