Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/8] regcache misc cleanup and refactor
Date: Fri, 27 Oct 2017 09:31:00 -0000	[thread overview]
Message-ID: <1509096702-12202-1-git-send-email-yao.qi@linaro.org> (raw)

During the work of regcache rewriting, I find there are some minor
cleanups and refactors can go upstream first.  Each patch is quite
self-contained, but they may be dependent to previous patches in
this series, so I put all of them in one patch set.

Rebuild GDB with every patch applied accumulatively, and regress
tested on x86_64-linux.

*** BLURB HERE ***

Yao Qi (8):
  Remove regcache_descr fields sizeof_raw_register_status and
    sizeof_cooked_register_status
  Remove code wrapped by "#if 0"
  New method regcache::assert_regnum
  Remove regcache_descr::nr_raw_registers
  s/get_regcache_aspace (regcache)/regcache->aspace ()/g
  const-fy regcache::m_aspace
  const-fy regcache::m_readonly_p
  Construct readonly regcache without address space

 gdb/darwin-nat.c     |  2 +-
 gdb/frame.c          |  5 ++-
 gdb/infrun.c         | 42 ++++++++++++-------------
 gdb/jit.c            |  4 +--
 gdb/linux-nat.c      |  8 ++---
 gdb/ppc-linux-tdep.c |  5 ++-
 gdb/record-full.c    |  7 ++---
 gdb/regcache.c       | 88 +++++++++++++++++++---------------------------------
 gdb/regcache.h       | 20 ++++++------
 9 files changed, 75 insertions(+), 106 deletions(-)

-- 
1.9.1


             reply	other threads:[~2017-10-27  9:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27  9:31 Yao Qi [this message]
2017-10-27  9:31 ` [PATCH 3/8] New method regcache::assert_regnum Yao Qi
2017-10-27  9:31 ` [PATCH 4/8] Remove regcache_descr::nr_raw_registers Yao Qi
2017-10-31 14:27   ` Simon Marchi
2017-11-02 15:20     ` Yao Qi
2017-10-27  9:31 ` [PATCH 1/8] Remove regcache_descr fields sizeof_raw_register_status and sizeof_cooked_register_status Yao Qi
2017-10-27  9:32 ` [PATCH 5/8] s/get_regcache_aspace (regcache)/regcache->aspace ()/g Yao Qi
2017-10-27  9:32 ` [PATCH 6/8] const-fy regcache::m_aspace Yao Qi
2017-10-31 14:19   ` Simon Marchi
2017-11-01  9:43     ` Yao Qi
2017-11-01 14:00       ` Simon Marchi
2017-11-01 14:35         ` Yao Qi
2017-10-27  9:32 ` [PATCH 7/8] const-fy regcache::m_readonly_p Yao Qi
2017-10-27  9:32 ` [PATCH 8/8] Construct readonly regcache without address space Yao Qi
2017-10-31 14:35   ` Simon Marchi
     [not found]     ` <CAH=s-PMFXtwS-3J9et_onyEOCUL9P-AgO9V=pBt60neQn67g9g@mail.gmail.com>
2017-10-31 18:04       ` Simon Marchi
2017-10-27  9:32 ` [PATCH 2/8] Remove code wrapped by "#if 0" Yao Qi

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=1509096702-12202-1-git-send-email-yao.qi@linaro.org \
    --to=qiyaoltc@gmail.com \
    --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