public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mjw@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: [PATCH] dwarf.h: Remove non-existing DW_TAG_mutable_type.
Date: Thu, 19 Jun 2014 12:03:01 +0200	[thread overview]
Message-ID: <1403172181.5528.12.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: 53A1DEF1.6080906@redhat.com

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

On Wed, 2014-06-18 at 11:48 -0700, Josh Stone wrote:
> On 06/18/2014 11:38 AM, Mark Wielaard wrote:
> > And a future version of DWARF might
> > use the number for a completely different purpose.
> 
> The issue you linked says this:
> 
>    Remove DW_TAG_mutable_type from Appendix A (Figure 17)
>    (Make sure not to reassign the number 0x3e to another tag.
>     Perhaps we should leave the table entry in there with
>     an "unused" marker in place of DW_TAG_mutable_type.
> 
> So it seems they intend to leave that number out forever.

They might and that might be a good thing. Although I don't know of any
producer that ever produced it since it was for a concept that didn't
really exist in any language. Note that the extra comments didn't end up
in the final spec. All that was officially done was remove the name. All
I am proposing is we do the same since the name should never have been
there in the first place. I'll add a comment instead saying the value is
reserved.

Cheers,

Mark


             reply	other threads:[~2014-06-19 10:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19 10:03 Mark Wielaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-06-22 17:31 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 15:48 Josh Stone
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=1403172181.5528.12.camel@bordewijk.wildebeest.org \
    --to=mjw@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).