public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Dave Brolley <brolley@redhat.com>
To: Ronald Hecht <ronald.hecht@uni-rostock.de>
Cc: cgen@sourceware.org
Subject: Re: Simulator: base_insn and insn in decode.c
Date: Mon, 14 Aug 2006 20:34:00 -0000	[thread overview]
Message-ID: <44E0DE39.9090702@redhat.com> (raw)
In-Reply-To: <44D30B5A.6070304@uni-rostock.de>

I've been on vacation....

Ronald Hecht wrote:

>> The test around the goto is intended to make sure that the untested 
>> base_insn bits are as expected. It needs to be there, otherwise, 
>> invalid insns get recognized as valid ones. However, it would seem 
>> that the test should be against base_insn and not against 
>> entire_insn. I'll have a look at some other cgen simulators, 
>> including those which use SID to make sure that this assertion holds 
>> water. It probably hasn't come up until now, since most sims I have 
>> seen are able to pass the same value for base_insn and entire_insn.
>>
>> Dave
>>
>
>
> I agreee. The test should be against base_insn. But then it still 
> seems to be double-checking against the same, or not?

No it's not a redundant test. The decoder only tests enough bits in the 
switch to uniquely separate the valid insns. There may be invalid bit 
patterns (i.e. unused opcodes) that still match. The secondary test 
makes sure that *all* of the opcode bits in the insn are tested.

Dave

      reply	other threads:[~2006-08-14 20:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 11:58 Ronald Hecht
2006-08-03 21:55 ` Dave Brolley
2006-08-03 22:08   ` Dave Brolley
2006-08-07 14:39     ` Ronald Hecht
2006-08-07 14:53     ` Ronald Hecht
2006-08-14 21:19       ` Dave Brolley
2006-08-15  8:39         ` Ronald Hecht
2006-08-04  8:51   ` Ronald Hecht
2006-08-14 20:34     ` Dave Brolley [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=44E0DE39.9090702@redhat.com \
    --to=brolley@redhat.com \
    --cc=cgen@sourceware.org \
    --cc=ronald.hecht@uni-rostock.de \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).