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: gdb-patches@sourceware.org
Subject: Re: [commit] Rename frame_pc_unwind and frame_unwind_id
Date: Tue, 15 Jul 2008 19:22:00 -0000	[thread overview]
Message-ID: <20080715192213.GC3094@caradoc.them.org> (raw)
In-Reply-To: <200807151908.m6FJ8YK3001326@brahms.sibelius.xs4all.nl>

On Tue, Jul 15, 2008 at 09:08:34PM +0200, Mark Kettenis wrote:
> > Date: Tue, 15 Jul 2008 15:01:25 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > 
> > This patch is the first non-trivial change in inlining support, and
> > readily separable.
> 
> Non-trivial...
> 
> > The users of frame_unwind_id and frame_pc_unwind are all either
> > inferior control, trying to find the caller / return address of a new
> > function, or trampoline handling.  I audited all of the uses, and the
> > right behavior in every one of them is to ignore any inlined functions
> > at the current location.  A future patch, the one adding inlined
> > frames, will make the corresponding change to frame_unwind_caller_id
> > and frame_unwind_caller_pc.  For now, I've just renamed them to
> > indicate the correct expectations.
> 
> ...so cann't we discuss this first please?

Sorry.  Want me to back it out?  I'm not going to commit anything
further; I've just posted the meat of the patch, which is harder to
separate.

I'm interested in your comments (about this patch or the larger one).

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-07-15 19:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 19:01 Daniel Jacobowitz
2008-07-15 19:09 ` Mark Kettenis
2008-07-15 19:22   ` Daniel Jacobowitz [this message]
2008-07-15 22:41     ` Mark Kettenis
2008-07-15 23:29       ` Daniel Jacobowitz

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=20080715192213.GC3094@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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