Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Kaushik Phatak <Kaushik.Phatak@kpitcummins.com>
Cc: Yao Qi <yao@codesourcery.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA 3/5] New port: CR16: gdb port
Date: Thu, 22 Nov 2012 17:50:00 -0000	[thread overview]
Message-ID: <20121122175010.GG9964@adacore.com> (raw)
In-Reply-To: <C6CA53A2A46BA7469348BDBD663AB65845B614E5@KCHJEXMB02.kpit.com>

> > +      allWords =
> > Can you please void using the mixed-cap style for variables?
> This variable along with currInsn suffer from the same problem. However, they
> have been borrowed from existing code from opcodes/cr16-dis.c
> May I leave them here as is for now as it is used at several places in cr16-dis.c?

Yes. I thought it was a variable declared inside GDB. This is fine.

> 2012-11-20 Kaushik Phatak  <kaushik.phatak@kpitcummins.com>
> 
> 	gdb/Changelog
> 	* configure.tgt: Handle cr16*-*-*linux and cr16*-*-*.
> 	* cr16-linux-tdep.c: New file.
> 	* cr16-tdep.c: New file.
> 	* cr16-tdep.h: New file.

A couple of very very minor nits. Pre-approved with the changes
requested below. Once you get approval for the BFD bits, you may
commit this patch. When you do, can you send us a notification,
as well as a copy of the patch that you commit (because it is
going to be different from the one posted here).

> +  if (p->has_frame_ptr)
> +    {
> +      CORE_ADDR fp = get_frame_register_unsigned (this_frame, CR16_FP_REGNUM);
> +      return fp - p->frame_ptr_offset;
> +    }
> +  else
> +    {
> +      CORE_ADDR sp = get_frame_register_unsigned (this_frame, CR16_SP_REGNUM);
> +      return sp - p->frame_size;
> +    }

Missing empty line after variable declaration in both blocks.

> +};	

Can you remov the trailing spaces?

Thank you,
-- 
Joel


  reply	other threads:[~2012-11-22 17:50 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-04 10:22 Kaushik Phatak
2012-10-04 14:48 ` Joel Brobecker
2012-10-05 11:44   ` Kaushik Phatak
2012-10-05 12:21     ` Joel Brobecker
2012-10-09 13:20       ` Kaushik Phatak
2012-10-08  6:59 ` Yao Qi
2012-10-09 15:03   ` Kaushik Phatak
2012-10-22 22:41     ` Joel Brobecker
2012-10-23 13:03       ` Kaushik Phatak
2012-10-23 13:55         ` Joel Brobecker
2012-10-26  5:15           ` Kaushik Phatak
2012-11-15 17:43             ` Joel Brobecker
2012-11-20 13:01               ` Kaushik Phatak
2012-11-22 17:50                 ` Joel Brobecker [this message]
2013-01-08 10:02                   ` Kaushik Phatak
2013-01-15  9:31                   ` Kaushik Phatak
2013-01-17  8:59                     ` Joel Brobecker
2013-01-18  7:41                       ` Kaushik Phatak
2013-01-18 14:17                         ` Joel Brobecker
2013-01-22 13:49                           ` Kaushik Phatak
2013-01-22 15:43                             ` Pedro Alves
2013-01-23 14:22                               ` Kaushik Phatak
2013-01-23 14:26                                 ` Pedro Alves
2013-01-23 15:34                                 ` Pedro Alves
2013-06-19 13:30                                   ` Kaushik Phatak
2013-06-25 18:42                                     ` Pedro Alves
2013-06-26  7:08                                       ` Kaushik Phatak
2013-06-26 10:37                                         ` Pedro Alves
2013-01-18 18:25                       ` Pedro Alves

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=20121122175010.GG9964@adacore.com \
    --to=brobecker@adacore.com \
    --cc=Kaushik.Phatak@kpitcummins.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.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