Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: uweigand@de.ibm.com, gdb-patches@sourceware.org
Subject: Re: [rfc/rft] Update remaining targets to value-based unwinding
Date: Sat, 28 Jun 2008 16:46:00 -0000	[thread overview]
Message-ID: <20080628164257.GA5827@caradoc.them.org> (raw)
In-Reply-To: <200805291645.m4TGjCRu006229@brahms.sibelius.xs4all.nl>

On Thu, May 29, 2008 at 06:45:12PM +0200, Mark Kettenis wrote:
> > Date: Thu, 29 May 2008 12:40:03 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > 
> > On Sun, May 18, 2008 at 10:15:25PM +0200, Ulrich Weigand wrote:
> > Hi Ulrich,
> > 
> > At this point I think you've gotten all the likely testing; is it time
> > to commit this?
> 
> I'm already looking at m88k; if you commit it Ulrich, can you leave
> that bit out?

Mark, did you have a chance to finish m88k?  Ulrich, how do you feel
about committing the non-m88k bits now?  Or I can take care of it if
that's easier.

I'm working on removing some warts from the version of inlined
function support I posted.  This requires careful reasoning about each
of the frame_*_unwind and frame_unwind_* methods, which is much easier
when they are not used in any unwinders; so I'm working from a tree
with Ulrich's patch applied.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-06-28 16:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19 15:16 Ulrich Weigand
2008-05-20  3:53 ` DJ Delorie
2008-05-20  7:54   ` Ulrich Weigand
2008-05-20 15:15     ` DJ Delorie
2008-05-20 15:17       ` Ulrich Weigand
2008-05-20 15:21         ` DJ Delorie
2008-05-30 11:19 ` Daniel Jacobowitz
2008-05-30 12:00   ` Mark Kettenis
2008-06-28 16:46     ` Daniel Jacobowitz [this message]
2008-06-28 17:44       ` Ulrich Weigand
2008-06-29  0:42       ` Mark Kettenis

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=20080628164257.GA5827@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=uweigand@de.ibm.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