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/2] Update cpu definition to handle ppc
Date: Sun, 12 Feb 2017 21:33:49 +0900	[thread overview]
Message-ID: <cover.1486902449.git.shorne@gmail.com> (raw)

Recently when testing qemu I found that the native gdb sim did not properly
set the ppc.  After some time of investigation I figured the best place to
fix this is by udating the pc set sematics in the cgen definition.

The patch is pretty simple, but maybe too much so?

I am sending this patch to see if anyone has a better idea of how to
support ppc updating in the gdb native sim.

-Stafford 

Stafford Horne (2):
  cpu: or1k: Set ppc on pc change
  sim: or1k: Regenerate sim files

 cpu/or1kcommon.cpu | 5 +++++
 sim/or1k/cpu32.c   | 4 ++--
 sim/or1k/cpu32.h   | 8 +++++++-
 3 files changed, 14 insertions(+), 3 deletions(-)

-- 
2.9.3


             reply	other threads:[~2017-02-12 12:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-12 12:33 Stafford Horne [this message]
2017-02-12 12:33 ` [OpenRISC] [PATCH 1/2] cpu: or1k: Set ppc on pc change Stafford Horne
2017-02-12 12:33 ` [OpenRISC] [PATCH 2/2] sim: or1k: Regenerate sim files 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.1486902449.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.