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
Subject: Re: [PATCH v3 0/5] sim port for OpenRISC
Date: Fri, 17 Mar 2017 05:58:00 -0000	[thread overview]
Message-ID: <20170317055801.GN2418@lianli.shorne-pla.net> (raw)
In-Reply-To: <cover.1489728532.git.shorne@gmail.com>

Note,

Some of these patches for generated files are too big for the mail
servers, if you want to see them all, please see:

The following changes since commit
b4fcfd3b4d173129207f804f5eee4557c788d66b:

  Automatic date update in version.in (2017-03-17 00:00:34 +0000)

are available in the git repository at:

  https://github.com/stffrdhrn/binutils-gdb.git tags/for-upstream

for you to fetch changes up to 26010e6737eddb5704d87494930f09afebc517ab:

  sim: testsuite: add testsuite for or1k sim (2017-03-17 14:22:43 +0900)


On Fri, Mar 17, 2017 at 02:39:06PM +0900, Stafford Horne wrote:
> Hello Again,
> 
> Please find attached the sim patches that allow to get a basic OpenRISC
> system running.  This was used to verify the OpenRISC gdb port.
> 
> The main author is Peter Gavin who should have his FSF copyright in place.
> 
> Request for comments on:
>  - The testcase has a few tests commented out. I do not plan to fix now,
>    but hopefully be addressed after upstreaming.
>  - Openrisc supports a l.rem instruction which has been implemented here
>    using the drem() function from libmath.  It seems no other functions use
>    libmath now, I hope this is ok.
> 
> Sim dejagnu tests were added specifically for openrisc and used to test
> this.  Please see the details of running the testsuite for sim below:
> 
> === sim Summary ===
> 
> # of expected passes            17
> /home/shorne/work/openrisc/build-gdb/sim/or1k/run 0.5
> 
> Thanks,
> -Stafford
> 
> Changes since v2
>  * Removed 64-bit implementation (reduced files)
>  * Removed cgen suffix patch
>  * Removed different builds for linux
>  * Removed unused macros
>  * Fixed gnu style issues pointed out by Mike
>  * Fixed copyrights (not Cygnus, added to each file)
> 
> Changes since v1
>  * Squashed sim patches into single sim patch
>  * Put Generated files in separate patch
>  * I have my sim/gdb copyright assignment complete
> 
> 
> Peter Gavin (3):
>   sim: cgen: add rem (remainder) function (needed for OR1K lf.rem.[sd])
>   sim: cgen: add mul-o1flag, mul-o2flag RTL functions to CGEN
>   sim: testsuite: add testsuite for or1k sim
> 
> Stafford Horne (2):
>   sim: or1k: add or1k target to sim
>   sim: or1k: Add generated files.
> 


      parent reply	other threads:[~2017-03-17  5:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-17  5:39 Stafford Horne
2017-03-17  5:39 ` [PATCH v3 2/5] sim: cgen: add mul-o1flag, mul-o2flag RTL functions to CGEN Stafford Horne
2017-03-17  5:39 ` [PATCH v3 1/5] sim: cgen: add rem (remainder) function (needed for OR1K lf.rem.[sd]) Stafford Horne
2017-03-17  5:40 ` [PATCH v3 5/5] sim: testsuite: add testsuite for or1k sim Stafford Horne
2017-03-17  5:40 ` [PATCH v3 3/5] sim: or1k: add or1k target to sim Stafford Horne
2017-03-17  5:58 ` Stafford Horne [this message]

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=20170317055801.GN2418@lianli.shorne-pla.net \
    --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