Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Pedro Alves <palves@redhat.com>
Cc: lgustavo@codesourcery.com,
	"'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>,
	Yao Qi <yao@codesourcery.com>
Subject: Re: [PATCH, gdbserver] Further cleanup of FDPIC/DSBT divergences
Date: Tue, 25 Jun 2013 16:26:00 -0000	[thread overview]
Message-ID: <201306251224.26392.vapier@gentoo.org> (raw)
In-Reply-To: <51C9B0BA.20707@redhat.com>

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

On Tuesday 25 June 2013 11:01:14 Pedro Alves wrote:
> can all be combined?  I'm confused on the current state
> of bfin solib debugging -- it is still depending on out of
> tree patches?

yes :/.  i tried to rewrite solib-frv.c to a solib-fdpic.c which frv & bfin 
then used, but haven't had a chance to ever really get back to finishing it.  i 
don't really want to merge the change the Blackfin port uses since it just 
copies solib-frv.c to solib-bfin.c then runs like s/FRV/BFIN/g on it.

since i no longer work at ADI, it's Blackfin stuff is a hobby now, so "boring" 
mechanical work like this isn't high on my list :x.
-mike

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

      parent reply	other threads:[~2013-06-25 16:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 18:57 Luis Machado
2013-06-24 13:47 ` Yao Qi
2013-06-24 14:25   ` Luis Machado
2013-08-08 16:41     ` Luis Machado
2013-08-09 15:08       ` Pedro Alves
2013-08-09 17:20         ` Luis Machado
2013-08-10  0:33           ` Yao Qi
2013-08-12 13:41             ` Luis Machado
2013-08-12 14:06               ` Pedro Alves
2013-08-26  5:31           ` Mike Frysinger
2013-06-24 16:17 ` Mike Frysinger
2013-06-25 15:03 ` Pedro Alves
2013-06-25 15:04   ` Luis Machado
2013-06-25 16:26   ` Mike Frysinger [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=201306251224.26392.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@codesourcery.com \
    --cc=palves@redhat.com \
    --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