Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Roland McGrath <mcgrathr@google.com>, GDB <gdb-patches@sourceware.org>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [PATCH users/roland/osabi] Recognize GNU .note.ABI-tag values 5 (syllable) and 6 (nacl)
Date: Fri, 29 May 2015 10:29:00 -0000	[thread overview]
Message-ID: <55683F9E.7020902@redhat.com> (raw)
In-Reply-To: <CAB=4xhpRRhMYF7-FtsYuTdCSn3fNOB1gOT_xjYaS11jJ6myGHw@mail.gmail.com>

On 05/29/2015 02:10 AM, Roland McGrath wrote:
> These two values are assigned in glibc trunk (5 has been assigned to
> syllable for several years, and 6 is quite recent).  I don't actually know
> anything about Syllable, but IMHO it makes sense for the other GNU packages
> that think about these values at all (binutils/gdb) to grok all the values
> that exist in the GNU package that owns this number space (libc).
> 
> OK for trunk and gdb's 7.9 branch?  (I don't really care about the readelf
> change, but I'm happy to put it on binutils' 2.25 branch if anyone thinks
> it's worthwhile.)

I think adding the constants to include/elf/common.h, and making
generic_elf_osabi_sniff_abi_tag_sections recognize syllable and nacl,
avoiding the internal_error (or warning after your other patch) is OK
and could go to the 7.9 branch.  Please split that out to a separate patch.

The rest of the gdb bits can be considered for trunk.  I don't think we want
GDB_OSABI_SYLLABLE exposed to the rest of the gdb (I don't know anything
about Syllable either), and to users (both "set osabi" and xml target
descriptions).  We may need to expose GDB_OSABI_NACL, but that's probably
best added along with the nacl port, assuming there's one.

Thanks,
Pedro Alves


  parent reply	other threads:[~2015-05-29 10:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29  1:10 Roland McGrath
2015-05-29  9:58 ` Nicholas Clifton
2015-05-29 16:15   ` Roland McGrath
2015-05-29 10:29 ` Pedro Alves [this message]
2015-05-29 16:47   ` Roland McGrath
2015-05-29 17:07     ` Pedro Alves

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=55683F9E.7020902@redhat.com \
    --to=palves@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mcgrathr@google.com \
    /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