public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Pinski <apinski@cavium.com>
To: gdb-patches@sourceware.org, binutils@sourceware.org
Cc: Andrew Pinski <apinski@cavium.com>
Subject: [PATCH 0/3] Support AARCH64 ILP32 for gdb
Date: Tue, 30 Aug 2016 00:26:00 -0000	[thread overview]
Message-ID: <1472516750-30743-1-git-send-email-apinski@cavium.com> (raw)

This patch set implements the basic support needed
to debug AARCH64 ILP32 programs under Linux.
This does not implement the full needed support
like for syscalls or core dump (both are still in flux).
But what is provided here is not influx at all and is indepedent
of any changes could happen to the Linux kernel or glibc.

Thanks,
Andrew Pinski

Andrew Pinski (3):
  Move AARCH64 ILP32 rejection handling
  Add ILP32 support to gdb.
  Handle ILP32 AARCH64 correctly for gdbserver

 bfd/ChangeLog                       |   8 ++
 bfd/cpu-aarch64.c                   |  28 +-----
 bfd/elfnn-aarch64.c                 |  17 +++-
 gdb/ChangeLog                       |  23 +++++
 gdb/aarch64-linux-tdep.c            |   8 +-
 gdb/aarch64-tdep.c                  |  23 ++++-
 gdb/aarch64-tdep.h                  |   3 +
 gdb/features/Makefile               |   4 +-
 gdb/features/aarch64_ilp32-core.xml |  67 +++++++++++++
 gdb/features/aarch64_ilp32.c        | 191 ++++++++++++++++++++++++++++++++++++
 gdb/features/aarch64_ilp32.xml      |  14 +++
 gdb/gdbserver/ChangeLog             |  19 ++++
 gdb/gdbserver/Makefile.in           |   6 ++
 gdb/gdbserver/configure.srv         |   7 +-
 gdb/gdbserver/linux-aarch64-ipa.c   |  11 ++-
 gdb/gdbserver/linux-aarch64-low.c   |  10 +-
 gdb/regformats/aarch64_ilp32.dat    |  73 ++++++++++++++
 17 files changed, 474 insertions(+), 38 deletions(-)
 create mode 100644 gdb/features/aarch64_ilp32-core.xml
 create mode 100644 gdb/features/aarch64_ilp32.c
 create mode 100644 gdb/features/aarch64_ilp32.xml
 create mode 100644 gdb/regformats/aarch64_ilp32.dat

-- 
2.7.4

             reply	other threads:[~2016-08-30  0:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30  0:26 Andrew Pinski [this message]
2016-08-30  0:26 ` [PATCH 2/3] Add ILP32 support to gdb Andrew Pinski
2016-08-30  7:44   ` Andreas Schwab
2016-09-01  4:21     ` Andrew Pinski
2016-09-01  7:41       ` Andreas Schwab
2016-08-30  0:26 ` [PATCH 3/3] Handle ILP32 AARCH64 correctly for gdbserver Andrew Pinski
2016-08-30  8:01   ` Andreas Schwab
2016-08-31 10:42   ` Pedro Alves
2016-08-31 12:58     ` Yao Qi
2016-08-31 20:02       ` Andrew Pinski
2016-08-30  0:26 ` [PATCH 1/3] Move AARCH64 ILP32 rejection handling Andrew Pinski
2016-09-01  7:37 ` [PATCH v2 0/3] Support AARCH64 ILP32 for gdb Andrew Pinski
2016-09-01  7:36   ` [PATCH 2/3] Add ILP32 support to gdb Andrew Pinski
2016-09-01  9:50     ` Andreas Schwab
2016-09-01 13:13     ` Yao Qi
2016-09-01  7:37   ` [PATCH 1/3] Move AARCH64 ILP32 rejection handling Andrew Pinski
2016-09-01  9:43     ` Richard Earnshaw (lists)
2016-09-01  7:37   ` [PATCH 3/3] Handle ILP32 AARCH64 correctly for gdbserver Andrew Pinski
2016-09-01  8:32     ` Andreas Schwab

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=1472516750-30743-1-git-send-email-apinski@cavium.com \
    --to=apinski@cavium.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@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).