From: Doug Evans <dje@sebabeach.org>
To: Masaki Muranaka <monaka@monami-software.com>
Cc: cgen@sourceware.org
Subject: Re: [RFC] FR60/80 support.
Date: Sun, 12 Jul 2009 15:39:00 -0000 [thread overview]
Message-ID: <4A5A03B2.8030103@sebabeach.org> (raw)
In-Reply-To: <D5DD11F3-2DA5-43B8-8AF5-A5048A168BB8@monami-software.com>
Masaki Muranaka wrote:
> Hello,
>
> Recently I'm trying to add FR60 and FR80 support based on FR30.
> I've already succeed to assemble with gas and disassemble with objdump.
>
> I'd like to contribute it but I'm not sure if my code is acceptable quality, because I'm new to cgen hack.
>
> Could anyone review attached patch and give comment?
> I'll post whole patch (includes gas/binutils) after this review.
>
>
> --
> Masaki Muranaka
> Monami software
>
>
Hi.
The patch is basically fine.
I have a few minor comments.
The comments in this part are pushed over a bit too far, they wrap on my
screen when there's no need.
+ ; `state' is a list of variables
for recording model state
+ (state
+ ; bit mask of h-gr registers
loaded from memory by previous insn
+ (load-regs UINT)
+ ; bit mask of h-gr registers
loaded from memory by current insn
+ (load-regs-pending UINT)
+ )
I think you want (set Ri (c-raw-call WI "..." Ri)).
[I realize the fr30 simulator has been deleted from the gdb tree.]
+(dni srch0
+ "srch0 Ri"
+ ((MACH fr80))
+ "srch0 $Ri"
+ (+ OP1_9 OP2_7 OP3_C Ri)
+ (c-raw-call WI "fr30_bitsearch0" Ri)
+ ()
+)
+
+(dni srch1
+ "srch1 Ri"
+ ((MACH fr80))
+ "srch1 $Ri"
+ (+ OP1_9 OP2_7 OP3_D Ri)
+ (c-raw-call WI "fr30_bitsearch1" Ri)
+ ()
+)
+
+
+(dni srchc
+ "srchc Ri"
+ ((MACH fr80))
+ "srchc $Ri"
+ (+ OP1_9 OP2_7 OP3_E Ri)
+ (c-raw-call WI "fr30_bitsearchc" Ri)
+ ()
+)
prev parent reply other threads:[~2009-07-12 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 0:27 Masaki Muranaka
2009-07-12 15:39 ` Doug Evans [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=4A5A03B2.8030103@sebabeach.org \
--to=dje@sebabeach.org \
--cc=cgen@sourceware.org \
--cc=monaka@monami-software.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).