From: Joel Brobecker <brobecker@adacore.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Add support for the Renesas rl78 architecture
Date: Thu, 26 Jan 2012 06:21:00 -0000 [thread overview]
Message-ID: <20120126045648.GT31383@adacore.com> (raw)
In-Reply-To: <20120125165800.5351c291@mesquite.lan>
Hi Kevin,
> Comments?
FWIW, I took a quick look at the code, although I don't know anything
about this architecture. You took the time to comment it nicely,
I also appreciate that.
> gdb/ChangeLog:
>
> * configure.tgt (rl78-*-elf): New target.
> * rl78-tdep.c: New file.
>
> include/gdb/ChangeLog:
>
> * sim-rl78.h: New file.
For the GDB bits, my only comments are with the coding style:
- There should be an empty line between a function description
and the start of its definition.
- There should be an empty line after variable declarations
- I noticed that you exceeded the 80 characters line size
a few times
- I think you want the opening curly brace on the next line
at the same column as the previous one (not indented 2 characters):
> +/* Implement the "register_name" gdbarch method. */
> +static const char *
> +rl78_register_name (struct gdbarch *gdbarch, int regnr)
> +{
> + static const char *const reg_names[] = {
> + "bank0_r0",
and
> +enum sim_rl78_regnum
> + {
> + sim_rl78_bank0_r0_regnum,
> + sim_rl78_bank0_r1_regnum,
> + sim_rl78_bank0_r2_regnum,
That's all I can really say.
--
Joel
next prev parent reply other threads:[~2012-01-26 4:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 1:21 Kevin Buettner
2012-01-26 2:24 ` Mike Frysinger
2012-01-26 9:18 ` Pedro Alves
2012-01-26 16:59 ` Kevin Buettner
2012-01-26 19:16 ` Mike Frysinger
2012-01-26 6:21 ` Joel Brobecker [this message]
2012-01-26 21:50 ` Sergio Durigan Junior
2012-01-26 23:24 ` Kevin Buettner
2012-01-27 0:23 ` Kevin Buettner
2012-01-27 2:02 ` Mike Frysinger
2012-01-27 5:48 ` Joel Brobecker
2012-01-30 22:44 ` Kevin Buettner
2012-01-30 3:11 ` Yao Qi
2012-01-30 23:05 ` Kevin Buettner
2012-01-30 23:58 ` Kevin Buettner
2012-02-04 6:06 ` Kevin Buettner
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=20120126045648.GT31383@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.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