Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Doug Evans <dje@google.com>
Cc: Simon Marchi <simon.marchi@polymtl.ca>,
	GDB patches <gdb-patches@sourceware.org>,
	Openrisc <openrisc@lists.librecores.org>,
	Mike Frysinger <vapier@gentoo.org>
Subject: Re: [PATCH v5 3/6] sim: or1k: add or1k target to sim
Date: Tue, 10 Oct 2017 23:03:00 -0000	[thread overview]
Message-ID: <20171010230323.GD2958@lianli.shorne-pla.net> (raw)
In-Reply-To: <001a114a9bbe18b046055b2055bc@google.com>

On Mon, Oct 09, 2017 at 05:15:08PM +0000, Doug Evans wrote:
> Simon Marchi writes:
>  > On 2017-10-05 09:49 AM, Stafford Horne wrote:
>  > > This adds the OpenRISC 32-bit sim target.  The OpenRISC sim is a CGEN
>  > > based sim so the bulk of the code is generated from the .cpu files by
>  > > CGEN.  The engine decode and execute logic in mloop uses scache with
>  > > pseudo-basic-block extraction and supports both full and fast (switch)
>  > > modes.
>  > > 
>  > > The sim does not implement an mmu at the moment.  The sim does implement
>  > > fpu instructions via the common sim-fpu implementation.
>  > > 
>  > > sim/ChangeLog:
>  > > 
>  > > 2017-09-13  Stafford Horne  <shorne@gmail.com>
>  > > 	    Peter Gavin  <pgavin@gmail.com>
>  > > 
>  > > 	* configure.tgt: Add or1k sim.
>  > > 	* or1k/Makefile.in: New file.
>  > > 	* or1k/configure.ac: New file.
>  > > 	* or1k/mloop.in: New file.
>  > > 	* or1k/or1k-sim.h: New file.
>  > > 	* or1k/or1k.c: New file.
>  > > 	* or1k/sim-if.c: New file.
>  > > 	* or1k/sim-main.h: New file.
>  > > 	* or1k/traps.c: New file.
>  > > ...
>  > > 
>  > > +#define CHECK_SPR_FIELD(GROUP, INDEX, FIELD, test)                      \
>  > > +  do {                                                                  \
>  > > +    USI field = GET_H_##SYS##_##INDEX##_##FIELD ();                     \
>  > > +    if (!(test)) {                                                      \
>  > > +      sim_io_eprintf(sd, "WARNING: unsupported %s field in %s register: 0x%x\n", \
>  > 
>  > 80 columns.
> 
> fwiw, I don't mind the odd >80 column limit breaker.
> Moving the string to the next line may just work,
> but if it doesn't it's fine by me to just leave it.

Thanks for this and the other comments.  I will get them fixed up and a new
version sent.

-Stafford


  reply	other threads:[~2017-10-10 23:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09 17:15 Doug Evans via gdb-patches
2017-10-10 23:03 ` Stafford Horne [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-10-05 13:49 [PATCH v5 0/6] sim port for OpenRISC Stafford Horne
2017-10-05 13:49 ` [PATCH v5 3/6] sim: or1k: add or1k target to sim Stafford Horne
2017-10-07 21:15   ` Simon Marchi
2017-10-09 13:03     ` Stafford Horne
2017-10-09 13:33       ` Simon Marchi

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=20171010230323.GD2958@lianli.shorne-pla.net \
    --to=shorne@gmail.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=openrisc@lists.librecores.org \
    --cc=simon.marchi@polymtl.ca \
    --cc=vapier@gentoo.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