From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Mike Frysinger <vapier@gentoo.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH][SIM] Add RXv2 simulation
Date: Wed, 08 Apr 2015 05:54:00 -0000 [thread overview]
Message-ID: <87bniz5fmz.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <20150408030943.GS16816@vapier>
At Tue, 7 Apr 2015 23:09:43 -0400,
Mike Frysinger wrote:
>
> [1 <text/plain; utf-8 (quoted-printable)>]
> On 07 Apr 2015 15:00, Yoshinori Sato wrote:
> > This patches added new instructions simulation for RX archtecture.
>
> please add some tests. if you look in sim/testsuite/sim/, you should be able to
> copy over something simple like mcore and then write a few basic .s files to
> test the new insns.
>
OK.
> just style comments otherwise -- i'm not familiar with the RX ISA
>
> > + tprintf("sqrt(%g) = %g\n", da, sqrt(da));
>
> all calls need a space before the (
> tprintf ("sqrt(%g) = %g\n", da, sqrt (da));
>
> this comes up a few times in your patch
>
> > + /* Less than 0.49999 */
>
> GNU style comments have a period at the end followed by two spaces:
> /* Less than 0.49999. */
>
> this comes up a few times in your patch
>
> > + whole_bits ++;
>
> no space before the ++ operator
>
> this comes up a few times in your patch
>
> > + while (! (whole_bits & 0x80000000UL))
>
> no space after the !
>
> > + if (tag) { printf (tag); tag = 0; }
>
> i guess not really a new problem, but you're changing this code so you might as
> well fix it, but this should not be one line
Thanks comment.
I'll fix next patches.
> -mike
> [2 Digital signature <application/pgp-signature (7bit)>]
> No public key for 41633B9FE837F581 created at 2015-04-08T12:09:43+0900 using RSA
prev parent reply other threads:[~2015-04-08 5:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 6:00 Yoshinori Sato
2015-04-08 3:09 ` Mike Frysinger
2015-04-08 5:54 ` Yoshinori Sato [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=87bniz5fmz.wl-ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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