Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, toolchain-devel@blackfin.uclinux.org
Subject: Re: [PATCH v4] gdb: bfin: new port
Date: Wed, 15 Dec 2010 19:40:00 -0000	[thread overview]
Message-ID: <201012151439.03130.vapier@gentoo.org> (raw)
In-Reply-To: <201012151917.03834.pedro@codesourcery.com>

[-- Attachment #1: Type: Text/Plain, Size: 1344 bytes --]

On Wednesday, December 15, 2010 14:17:03 Pedro Alves wrote:
> On Wednesday 15 December 2010 16:47:25, Mike Frysinger wrote:
> > +bfin-*-*)
> > +       # Target: Blackfin
> > +       gdb_target_obs="bfin-tdep.o bfin-linux-tdep.o linux-tdep.o"
> > +       ;;
> 
> should probably be:
> 
> bfin-*-uclinux*)
>        # Target: Blackfin running uclinux
>        gdb_target_obs="bfin-tdep.o bfin-linux-tdep.o linux-tdep.o"
>        ;;
> bfin-*-*)
>        # Target: Blackfin
>        gdb_target_obs="bfin-tdep.o"
>        ;;
> 
> The top-level src/configure.ac seems to actually use
> bfin*-*-uclinux* (extra star).

we run Linux.  uClinux is an old naming.  also, bfin-linux-uclibc is a 
supported target, so i tend to use bfin-*-*linux*.

in the past, any Blackfin gdb was sufficient to debug any Blackfin target, but 
i guess i could preserve this with --enable-targets=... ?

> > +         warning (_("Function Prologue not recognised; pc will point to
> > ENTRY_POINT of the function"));
> 
> way too long line.  write as, e.g.,
> 
>          warning (_("Function Prologue not recognised; "
>                     "pc will point to ENTRY_POINT of the function"));

yes it's long, but i thought the emphasis was on not breaking string literals.  
screws up grep and such.

the rest i've fixed locally
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2010-12-15 19:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15 16:48 Mike Frysinger
2010-12-15 16:48 ` [PATCH v4] gdbserver: " Mike Frysinger
2010-12-15 19:21   ` Pedro Alves
2010-12-15 19:17 ` [PATCH v4] gdb: " Pedro Alves
2010-12-15 19:40   ` Mike Frysinger [this message]
2010-12-15 19:51     ` Pedro Alves
2010-12-15 20:11       ` 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=201012151439.03130.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=toolchain-devel@blackfin.uclinux.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