From: Roland McGrath <mcgrathr@google.com>
To: Pedro Alves <palves@redhat.com>
Cc: GDB <gdb-patches@sourceware.org>
Subject: Re: [PATCH users/roland/osabi] Recognize GNU .note.ABI-tag values 5 (syllable) and 6 (nacl)
Date: Fri, 29 May 2015 16:47:00 -0000 [thread overview]
Message-ID: <CAB=4xhr8YL3tkjWbRnUb9nRk-uhB9ohCEW7d6=hD7HtrNk=omA@mail.gmail.com> (raw)
In-Reply-To: <55683F9E.7020902@redhat.com>
On Fri, May 29, 2015 at 3:29 AM, Pedro Alves <palves@redhat.com> wrote:
> I think adding the constants to include/elf/common.h,
I've already committed common.h based on the binutils approval.
> 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.
Do you mean just silently ignoring these values?
> 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.
OK. I'll ignore Syllable entirely, since I was only doing it for
completeness.
For NaCl, I'll investigate further before proposing something. We have a
patch that is mostly about x86 and needs some cleanup (or probably complete
rewriting). NaCl's x86-64 is particularly odd and I don't want to worry
about the weird cruft we have for that right now. At the moment, I'm
focused on on arm-nacl. NaCl is an all-remote target (the only kind of
"native" debugging interface available is a gdb stub). So there really is
almost nothing to do. But when I get some time I'll look into building
--target=arm-nacl on trunk and see what it needs.
Thanks,
Roland
next prev parent reply other threads:[~2015-05-29 16:47 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
2015-05-29 16:47 ` Roland McGrath [this message]
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='CAB=4xhr8YL3tkjWbRnUb9nRk-uhB9ohCEW7d6=hD7HtrNk=omA@mail.gmail.com' \
--to=mcgrathr@google.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).