Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: gdb-patches@sourceware.org
Cc: openrisc@lists.librecores.org,	Stafford Horne <shorne@gmail.com>
Subject: [PATCH v3 0/3] OpenRISC gdb port
Date: Thu, 22 Dec 2016 16:14:00 -0000	[thread overview]
Message-ID: <cover.1482413820.git.shorne@gmail.com> (raw)

Hello,

This is the openrisc port of GDB that has been in openrisc
repositories for a very long time. The main original author
was Jeremy Bennett as can be seen in file copyrights. Other
are willing to do what it takes for FSF copyright assignment.

This along with the sim patches are the last of what has not
made its way upstream. The patches are based on current gdb
git master branch.

I have run the testsuite and results are as follows:

# of expected passes            19241
# of unexpected failures        406
# of expected failures          29
# of known failures             57
# of unresolved testcases       2
# of untested testcases         190
# of unsupported tests          264

--
Changes from v2
 * Updates as per Yao's comments
  - Fix copyrights, jullien embecosm, remove embecosm
  - indentation to use gnu style (i.e. && and || on left)
  - Fix comments to use gnu style
  - Move some includes around
  - Remove constant variables, replace with constants
  - Remove doxygen on a few calls
  - Have only 1 space between type and var name
  - remove todo about 4 const
  - do fix *buf checks (use buf != NULL)
  - BP_MANIPULATION
  - Use the builtin types for reg register functions
  - or1k_iterate_over_regset_sections - remove no linux, no cores yet
 * Remove unimplements pseudo register functions
 * Remove spr commands as we can now get those via `info reg`

Changes from v1
 * Merged or1k-tdep.[ch] changes into a single commit
 * Futher fixes to change log bringing in history back to 2008
 * Fix doc issue on sw_breakpoint_from_kind


Franck Jullien (1):
  gdb: Add OpenRISC or1k and or1knd target support

Stafford Horne (1):
  gdb: testsuite: Add or1k l.nop inscruction

Stefan Wallentowitz (1):
  Add gdb for or1k build

 configure                             |    7 -
 configure.ac                          |    7 -
 gdb/configure.tgt                     |   12 +
 gdb/doc/gdb.texinfo                   |   68 ++
 gdb/or1k-tdep.c                       | 1436 +++++++++++++++++++++++++++++++++
 gdb/or1k-tdep.h                       |   57 ++
 gdb/testsuite/gdb.base/bp-permanent.c |    2 +
 7 files changed, 1575 insertions(+), 14 deletions(-)
 create mode 100644 gdb/or1k-tdep.c
 create mode 100644 gdb/or1k-tdep.h

-- 
2.7.4


             reply	other threads:[~2016-12-22 16:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-22 16:14 Stafford Horne [this message]
2016-12-22 16:14 ` [PATCH v3 3/3] Add gdb for or1k build Stafford Horne
2016-12-22 16:14 ` [PATCH v3 1/3] gdb: Add OpenRISC or1k and or1knd target support Stafford Horne
2016-12-23 21:21   ` Luis Machado
2016-12-25  1:31     ` Stafford Horne
2016-12-26 16:10       ` Luis Machado
2016-12-27 13:20         ` Stafford Horne
2016-12-22 16:14 ` [PATCH v3 2/3] gdb: testsuite: Add or1k l.nop inscruction Stafford Horne

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=cover.1482413820.git.shorne@gmail.com \
    --to=shorne@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=openrisc@lists.librecores.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