From: Michael Snyder <msnyder@redhat.com>
To: Kazu Hirata <kazu@cs.umass.edu>
Cc: gdb-patches@sources.redhat.com, dvenkat@noida.hcltech.com,
avolkov@transas.com, cagney@redhat.com
Subject: Re: h8/300 sim tests
Date: Tue, 08 Apr 2003 06:06:00 -0000 [thread overview]
Message-ID: <3E9266EE.6897739F@redhat.com> (raw)
In-Reply-To: <20030407.100240.21905392.kazu@cs.umass.edu>
Kazu Hirata wrote:
>
> Hi Michael,
>
> > I've been working on some tests for the h8/300 simulator, and I've
> > decided they're ready for contribution. I hope this framework will
> > make it easy for others to add tests (hint hint file i/o cmdline).
> > These are meant to go in a new directory sim/testsuite/sim/h8300.
>
> This is cool, especially because the simulator are not good at
> simulating instructions that gcc does not output. :-(
>
> > You'll immediately see from this that I'm also working on adding
> > the h8sx architecture. Look for that submission shortly. These
> > tests will work as is, without that submission, with just a few
> > failures (which probably represent existing bugs).
>
> Would you mind sharing some of the failures you've found?
Heck, I'll even send you patches. ;-)
You can run these tests yourself -- I think you'll see failures in
ldc/stc (patch to follow), and daa/das (not implemented yet), and
shal/shll (carry is wrong, patch to follow).
Install the patch in src/sim/testsuite/sim/h8300 (except for the
configure change, which goes in src/sim. Run configure, build,
install (required), and then cd build/sim/testsuite and run
make check RUNTESTFLAGS=allinsn.exp
It runs pretty quickly.
next prev parent reply other threads:[~2003-04-08 6:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3E917FF6.4699C121@redhat.com>
2003-04-07 14:03 ` Kazu Hirata
2003-04-08 6:06 ` Michael Snyder [this message]
2003-04-09 7:04 ` Michael Snyder
2003-04-12 18:40 ` Kazu Hirata
2003-04-12 20:00 ` Michael Snyder
2003-04-13 16:46 ` Michael Snyder
2003-04-16 4:55 D.Venkatasubramanian, Noida
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=3E9266EE.6897739F@redhat.com \
--to=msnyder@redhat.com \
--cc=avolkov@transas.com \
--cc=cagney@redhat.com \
--cc=dvenkat@noida.hcltech.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kazu@cs.umass.edu \
/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