All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH 0/5] Openrisc gdb patches after yao's comments
Date: Sat, 17 Dec 2016 01:02:50 +0900	[thread overview]
Message-ID: <cover.1481903617.git.shorne@gmail.com> (raw)

Hi All, 

I wanted to circulate these patches on the openrisc list first. These are in 
response to Yao's gdb patch review.

 - The first patch is baiscally format and comment updates as per gnu style. 
 - The second removes the unimplemented pseudo register functions
 - Next is the BIG one it removes the handling of target-description parsing
   and intercepting.  But this is as per the recommended way. May what is 
   questionable is how I hard code the reggroups.
 - Next removes the special spr commands.  I think or1ksim would need to be
   updated to work with the target-descriptor xml.
 - Last is just a cleanup.

The plan would be to squash all of these into the previous patch set I sent. 

Test results look ok.  Also I tested against openocd and I can reed sprs with
commands like `info reg upr` as expected.

                === gdb Summary ===

# 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
/home/shorne/work/openrisc/build-gdb/gdb/gdb version  7.12.50.20161122-git 

-Stafford

Stafford Horne (5):
  gdb: or1k: Updates suggested by yao in gdb review
  gdb: or1k: Remove pseudo registers
  or1k: gdb: Simplify handling of tdesc
  or1k: gdb: Remove spr commands
  gdb: or1k: Just have one number of registers

 gdb/configure.tgt         |   14 -
 gdb/or1k-tdep.c           | 2931 +++++++++------------------------------------
 gdb/or1k-tdep.h           |  389 +-----
 gdb/target-descriptions.c |   34 -
 gdb/target-descriptions.h |   12 -
 5 files changed, 549 insertions(+), 2831 deletions(-)

-- 
2.7.4



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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16 16:02 Stafford Horne [this message]
2016-12-16 16:02 ` [OpenRISC] [PATCH 1/5] gdb: or1k: Updates suggested by yao in gdb review Stafford Horne
2016-12-16 16:02 ` [OpenRISC] [PATCH 2/5] gdb: or1k: Remove pseudo registers Stafford Horne
2016-12-16 16:02 ` [OpenRISC] [PATCH 3/5] or1k: gdb: Simplify handling of tdesc Stafford Horne
2016-12-16 16:02 ` [OpenRISC] [PATCH 4/5] or1k: gdb: Remove spr commands Stafford Horne
2016-12-16 16:02 ` [OpenRISC] [PATCH 5/5] gdb: or1k: Just have one number of registers Stafford Horne
2016-12-16 16:12 ` [OpenRISC] [PATCH 0/5] Openrisc gdb patches after yao's comments 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.1481903617.git.shorne@gmail.com \
    --to=shorne@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.