From: Doug Evans <dje@sebabeach.org>
To: cgen@sourceware.org
Subject: xc16x.cpu insn issues
Date: Thu, 18 Jun 2009 17:54:00 -0000 [thread overview]
Message-ID: <4A3A7F5A.4020508@sebabeach.org> (raw)
Hi.
After adding (nop) to the "nop" instruction, I found a few other
instructions with missing semantics.
For now we could just make them all nops, and add FIXME's for srstm,etc.
I also found the "prior" insn with invalid semantics.
What should these insns be?
(define-pmacro (sysctrl name insn opc1 opc2 op1 op2 op3)
(dni name
(.str name "miscellaneous" )
((PIPE OS) (IDOC MISC))
(.str insn )
(+ opc1 opc2 (f-op-lbit4 op1) (f-op-bit4 op2) (f-data8 op3)
(f-op-bit8 op3))
(???) <<<
()
)
)
(sysctrl srstm srst OP1_11 OP2_7 4 8 183 )
(sysctrl idlem idle OP1_8 OP2_7 7 8 135)
(sysctrl pwrdnm pwrdn OP1_9 OP2_7 6 8 151)
(sysctrl diswdtm diswdt OP1_10 OP2_5 5 10 165)
(sysctrl enwdtm enwdt OP1_8 OP2_5 7 10 133)
(sysctrl einitm einit OP1_11 OP2_5 4 10 181)
(sysctrl srvwdtm srvwdt OP1_10 OP2_7 5 8 167 )
;s/w brk
; SBRK
(dni sbrk "sbrk"
((PIPE OS) (IDOC MISC))
"sbrk"
(+ OP1_8 OP2_12 (f-op-bit8 0))
(???) <<<
()
)
;prioritize register
;PRIOR Rwn,Rwm
(dni prior "add registers"
((PIPE OS) (IDOC ALU))
"prior $dr,$sr"
(+ OP1_2 OP2_11 dr sr)
(sequence ((HI count) (HI tmp1) (HI tmp2))
(set HI count (const 0))
(set HI tmp1 sr)
(set HI tmp2 (and tmp1 (const 32768)))
>> (cond HI
>> ((ne HI tmp2 (const 1)) (ne HI sr (const 0))
>> (sll HI tmp1 (const 1))
>> (set HI tmp2 (and tmp1 (const 32768)))
>> (set HI count (add HI count (const 1)))
>> )
>> )
(set HI dr count)
)
()
)
reply other threads:[~2009-06-18 17:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A3A7F5A.4020508@sebabeach.org \
--to=dje@sebabeach.org \
--cc=cgen@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).