Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org, toolchain-devel@blackfin.uclinux.org,
	Jie Zhang <jie.zhang@analog.com>
Subject: Re: [PATCH v2] gdb: bfin: new port
Date: Tue, 14 Dec 2010 06:03:00 -0000	[thread overview]
Message-ID: <20101214060247.GK2596@adacore.com> (raw)
In-Reply-To: <1291886957-12003-1-git-send-email-vapier@gentoo.org>

> 2010-11-16  Jie Zhang  <jie.zhang@analog.com>
> 
> 	* Makefile.in (ALLDEPFILES): Add bfin-tdep.c.
> 	(HFILES_NO_SRCDIR): Add bfin-tdep.h.

(ALL_TARGET_OBS): Add bfin-tdep.o

> 	* NEWS: Mention new Blackfin port.
> 	* bfin-tdep.c, bfin-tdep.h, config/bfin/bfin.mt: New files.
> 	* configure.tgt (bfin-*-*): Handle bfin targets.

The syscall file is also missing.

There are a couple of nits, highlighted below.  But the patch is
pre-approved with those nits fixed as suggested. One little issue,
though: Please make sure that Eli reviews the change in the NEWS
file before checking in that part of the patch (it can be done
separately).

> +#ifdef _DEBUG
> +      fprintf (stderr, "frameless pc case base %x\n", cache->base);
> +#endif

You forgot to remove the #ifdef DEBUG block...

> +/* Return the Blackfin ABI associated with GDBARCH.  */
> +static inline enum bfin_abi
> +bfin_abi (struct gdbarch *gdbarch)
> +{
> +  return gdbarch_tdep (gdbarch)->bfin_abi;
> +}

Please define that function in bfin-tdep.c, and put a declaration in
bfin-tdep.h instead.

-- 
Joel


  parent reply	other threads:[~2010-12-14  6:03 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09  9:29 Mike Frysinger
2010-12-09  9:31 ` [PATCH v2] gdbserver: " Mike Frysinger
2010-12-13 18:44   ` Pedro Alves
2010-12-13 19:24     ` Mike Frysinger
2010-12-14  9:37     ` Andrew Stubbs
2010-12-14 15:10       ` Mike Frysinger
2010-12-14 16:31         ` Pedro Alves
2010-12-14 16:58           ` Mike Frysinger
2010-12-14 17:16             ` Andrew Stubbs
2010-12-14 17:26               ` Mike Frysinger
2010-12-15 11:54                 ` Andrew Stubbs
2010-12-15 12:55                   ` [toolchain-devel] " Mike Frysinger
2010-12-15 13:17                     ` Andrew Stubbs
2010-12-14 17:40             ` Pedro Alves
2010-12-14 17:48               ` Mike Frysinger
2010-12-14 18:06                 ` Pedro Alves
2010-12-14 18:21                   ` Mike Frysinger
2010-12-15 16:54                     ` Mike Frysinger
2010-12-14  6:03 ` Joel Brobecker [this message]
2010-12-14 16:14   ` [PATCH v2] gdb: " Mike Frysinger
2010-12-14 20:43 ` [PATCH v3] " Mike Frysinger
2010-12-14 21:31   ` Pedro Alves
2010-12-14 22:01     ` Mike Frysinger
2010-12-15 13:02       ` Mike Frysinger
2010-12-15 16:53         ` Pedro Alves
2010-12-15 17:08           ` Mike Frysinger
2010-12-15 18:01             ` Pedro Alves
2010-12-15 18:38               ` Mike Frysinger
2010-12-15 18:42                 ` Pedro Alves
2010-12-15 18:16             ` Mike Frysinger
2010-12-15 18:25               ` Pedro Alves
2010-12-14 21:48   ` [PATCH v3] gdbserver: " Mike Frysinger
2010-12-14 23:03     ` Ralf Corsepius
2010-12-15  0:15       ` Mike Frysinger

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=20101214060247.GK2596@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jie.zhang@analog.com \
    --cc=toolchain-devel@blackfin.uclinux.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