Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jiri Gaisler <jiri@gaisler.se>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 00/22] Update of the SPARC SIS simulator
Date: Tue, 17 Feb 2015 14:41:00 -0000	[thread overview]
Message-ID: <54E352FB.6080701@gaisler.se> (raw)
In-Reply-To: <20150217085419.GH20008@vapier>


On 02/17/2015 09:54 AM, Mike Frysinger wrote:
> On 17 Feb 2015 08:44, Jiri Gaisler wrote:
>> This is a 22-part patch that brings the sis simulator into working
>> order, and adds support for emulation of the leon2 and leon3 cpus.
>>
>> The sis simulator was written by me in the mid 90's, to emulate the erc32
>> processor (SPARC V7). It was included into gdb by Cygnus (Stan Shebs?),
>> and adapted to also emulate the Fujistu Sparlite processor. The simulator
>> has not been actively maintained for about 15 years, and suffered some
>> bit-rot. It's primary use has been for RTEMS development. The erc32
>> processor is now becoming obsolete, and being replaced by leon2 and
>> leon3 cpus in many ESA and NASA missions. These patches will
>> allow sis to be useful again, and support the newer leon2/3 processor.
> it would be nice if there was a testsuite.  how are you verifying things
> continue to work and there are no regressions ?
>
> should be easy to add some basic .s files to verify insns ... lots of examples
> in the testsuite/sim/ subdirs already.
> -mike
I have a set of pre-compiled binaries to test for basic SPARC and FPU
compliance. On top of that, I run the RTEMS testsuite which is rather
extensive. Is it acceptable to drop a few SPARC binaries to the gdb
testuite/sim, or does it all have to be in source? The test applications
are typically written in C, so we would need a full C cross-compiler to
build them ...

Jiri.


  reply	other threads:[~2015-02-17 14:41 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17  7:45 Jiri Gaisler
2015-02-17  7:45 ` [PATCH 02/23] sim/erc32: corrected wrong CPU implementation and version ID in %psr Jiri Gaisler
2015-02-17 11:03   ` Mike Frysinger
2015-02-17  7:45 ` [PATCH 05/23] sim/erc32: remove unused defines in Makefile and switch off statistics Jiri Gaisler
2015-02-17 11:04   ` Mike Frysinger
2015-02-17  7:45 ` [PATCH 01/23] sim/erc32: Disassembly in stand-alone mode did not work due to API change Jiri Gaisler
2015-02-17 11:03   ` Mike Frysinger
2015-02-17  7:45 ` [PATCH 07/23] sim/erc32: file loading via command line did not work Jiri Gaisler
2015-02-17  9:09   ` Mike Frysinger
2015-02-17  7:45 ` [PATCH 10/23] sim/erc32: Switched emulated memory to host endian order Jiri Gaisler
2015-02-17  7:45 ` [PATCH 15/23] sim/erc32: access memory subsystem through struct memsys to allow multiple configurations Jiri Gaisler
2015-02-17  7:45 ` [PATCH 17/23] sim/erc32: Move local extern declarations into sis.h Jiri Gaisler
2015-02-17  7:45 ` [PATCH 04/23] sim/erc32: Add FPU support on x86_64 hosts Jiri Gaisler
2015-02-17  9:05   ` Mike Frysinger
2015-02-19 20:45     ` Jiri Gaisler
2015-02-22  4:40       ` Mike Frysinger
2015-02-22 21:43         ` Jiri Gaisler
2015-02-17  7:45 ` [PATCH 16/23] sim/erc32: use readline.h for readline types and functions Jiri Gaisler
2015-02-17  9:21   ` Mike Frysinger
2015-02-17  7:46 ` [PATCH 21/23] sim/erc32: add data watchpoint support for all cpu targets Jiri Gaisler
2015-02-17  7:46 ` [PATCH 19/23] sim/erc32: Added support for the Leon2 processor Jiri Gaisler
2015-02-17  7:46 ` [PATCH 13/23] sim/erc32: Fix a few compiler warnings Jiri Gaisler
2015-02-17 11:08   ` Mike Frysinger
2015-02-18 16:21     ` Jiri Gaisler
2015-02-18 16:51       ` Mike Frysinger
2015-02-17  7:46 ` [PATCH 20/23] sim/erc32: Updated documentation Jiri Gaisler
2015-02-17 11:03   ` Mike Frysinger
2015-02-17 15:52   ` Eli Zaretskii
2015-02-17  7:46 ` [PATCH 03/23] sim/erc32: Perform pseudo-init of system if binary starts from non-zero address Jiri Gaisler
2015-02-17  8:59   ` Mike Frysinger
2015-02-18 14:40     ` Jiri Gaisler
2015-02-18 16:53       ` Mike Frysinger
2015-02-19 16:11         ` Jiri Gaisler
2015-02-19 17:48           ` Mike Frysinger
2015-02-17  7:46 ` [PATCH 11/23] sim/erc32: use AC_C_BIGENDIAN to probe for host endian Jiri Gaisler
2015-02-17  9:19   ` Mike Frysinger
2015-02-17  7:46 ` [PATCH 08/23] sim/erc32: added -v and -vv command line switches for verbose output Jiri Gaisler
2015-02-17  9:13   ` Mike Frysinger
2015-02-17  7:46 ` [PATCH 14/23] sim/erc32: Use gdb callback for UART I/O when linked with gdb Jiri Gaisler
2015-02-17  7:46 ` [PATCH 09/23] sim/erc32: removed type mismatch compiler warnings Jiri Gaisler
2015-02-17  9:10   ` Mike Frysinger
2015-02-18 14:41     ` Jiri Gaisler
2015-02-18 16:57       ` Mike Frysinger
2015-02-17  7:46 ` [PATCH 12/23] sim/erc32: Use separate memory_iread() function for instruction fetching Jiri Gaisler
2015-02-17  7:46 ` [PATCH 18/23] sim/erc32: Add support for LEON3 processor emulation Jiri Gaisler
2015-02-17 15:58   ` Eli Zaretskii
2015-02-17  7:46 ` [PATCH 06/23] sim/erc32: Fix incorrect simulator performance report Jiri Gaisler
2015-02-17  9:07   ` Mike Frysinger
2015-02-17  7:46 ` [PATCH 22/23] Added watchpoint support to gdb simulator interface Jiri Gaisler
2015-02-17  8:54 ` [PATCH 00/22] Update of the SPARC SIS simulator Mike Frysinger
2015-02-17 14:41   ` Jiri Gaisler [this message]
2015-02-18  0:16     ` Mike Frysinger

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=54E352FB.6080701@gaisler.se \
    --to=jiri@gaisler.se \
    --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