Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kazu Hirata <kazu@cs.umass.edu>
To: msnyder@redhat.com
Cc: gdb-patches@sources.redhat.com, dvenkat@noida.hcltech.com,
	avolkov@transas.com, cagney@redhat.com
Subject: Re: h8/300 sim tests
Date: Sat, 12 Apr 2003 18:40:00 -0000	[thread overview]
Message-ID: <20030412.143919.126765664.kazu@cs.umass.edu> (raw)
In-Reply-To: <3E917FF6.4699C121@redhat.com>

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.

I just looked at the patch.  This is great!

But I am a little concerned about its size, though.  You've written
this macro.

+ 	.macro test_cc_clear
+ 	test_carry_clear
+ 	test_ovf_clear
+ 	test_zero_clear
+ 	test_neg_clear
+ 		; leaves H, I, U, and UI untested
+ 	.endm

but I still see a lot of

+ 	test_carry_clear	; H=0 N=0 Z=0 V=0 C=0
+ 	test_ovf_clear
+ 	test_zero_clear
+ 	test_neg_clear

In and.w.s, or.w.s, and xor.w.s, I see a nest of

+ .if (sim_cpu)			; non-zero means h8300h, s, or sx

which you probably didn't mean.

I think we should have more macros that test that registers have not
changed like test_gr_a5a5_0_7 and test_gr_a5a5_1_7.

Having said all these, maybe we can first commit your patch and then
work on CVS.  I am willing to help here.

Kazu Hirata


  parent reply	other threads:[~2003-04-12 18:40 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
2003-04-09  7:04   ` Michael Snyder
2003-04-12 18:40 ` Kazu Hirata [this message]
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=20030412.143919.126765664.kazu@cs.umass.edu \
    --to=kazu@cs.umass.edu \
    --cc=avolkov@transas.com \
    --cc=cagney@redhat.com \
    --cc=dvenkat@noida.hcltech.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@redhat.com \
    /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