From: "Edgar E. Iglesias" <edgar.iglesias@axis.com>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: edgar.iglesias@axis.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] CRIS sim and it's testsuite
Date: Mon, 22 Oct 2007 21:01:00 -0000 [thread overview]
Message-ID: <20071022204241.GA3330@edgar.underground.se.axis.com> (raw)
In-Reply-To: <200710221653.l9MGrdTQ021458@ignucius.se.axis.com>
On Mon, Oct 22, 2007 at 06:53:39PM +0200, Hans-Peter Nilsson wrote:
> > Date: Wed, 3 Oct 2007 16:58:48 +0200
> > From: "Edgar E. Iglesias" <edgar@axis.com>
>
> > I noticed that the condition code flags were not tested for
> > move-like insns on CRIS.
>
> Thanks for looking into this. Yes, the test_move_cc macro was
> totally fudged. I can only guess I stubbed it and meant to
> revisit that part but just forgot.
>
> Your change adds code to just test N and Z though the intention
> of test_move_cc is to also test C and V, for pre-v32. When
> fixing that, I had to adjust the jsr testcase as seen. I also
> noticed that there were more flaws in the neg test; the V and C
> flags should always be tested as it's an arithmetic insn and the
> formerly unused/untested values for V and C were wrong. Noting
> the lack of non-arithmetic V and C tests for v32, I added a new
> test-case to check that V and C aren't affected for v32, for
> some common insns and values. I'm not claiming full coverage
> there, just better than not testing V and C for v32 at all for
> those insns.
Thanks for taking care of all this H-P.
Best regards
--
Edgar E. Iglesias
Axis Communications AB
prev parent reply other threads:[~2007-10-22 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 14:58 Edgar E. Iglesias
2007-10-11 18:17 ` Daniel Jacobowitz
2007-10-12 3:54 ` Hans-Peter Nilsson
2007-10-22 16:09 ` Hans-Peter Nilsson
2007-10-22 16:56 ` Hans-Peter Nilsson
2007-10-22 21:01 ` Edgar E. Iglesias [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=20071022204241.GA3330@edgar.underground.se.axis.com \
--to=edgar.iglesias@axis.com \
--cc=gdb-patches@sourceware.org \
--cc=hans-peter.nilsson@axis.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