Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [unwind-20030108-branch] Add sentinel-frame + misc
Date: Fri, 10 Jan 2003 21:33:00 -0000	[thread overview]
Message-ID: <20030110213400.GA8623@nevyn.them.org> (raw)
In-Reply-To: <3E1E6C23.8050407@redhat.com>

On Fri, Jan 10, 2003 at 01:45:55AM -0500, Andrew Cagney wrote:
> with patch,
> 
> >This adds sentinal-frame.[hc] and then modifies the unwind code in frame.c 
> >so that it can exploit the fact that there is alway an extra frame beyond 
> >the inner most frame.  This has a dramatic effect on the unwind code - so 
> >much simpler!
> >
> >It doesn't do things like ensure that there is always a frame or create 
> >the inner most frame from the sentinel frame.
> >
> >To confuse the patch slightly, it also adjusts the id_unwind, pc_unwind 
> >and register_unwind function types.
> >
> >Andrew

Yeah!

I've just got one stylistic comment:

> -struct dummy_frame
> +struct frame_unwind_cache
>  {
> -  struct dummy_frame *next;
> +  struct frame_unwind_cache *next;


> @@ -555,8 +522,14 @@
>     If the value isn't here AND a value is needed, try the next inner
>     most frame.  */
>  
> +struct frame_unwind_cache
> +{
> +  void *regs[1];
> +};
> +

I know it makes some type-checking simpler, but naming all your private types
the same thing is a real nuisance when using this lame "GDB" thing on
the code afterwards.  Must we?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-01-10 21:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-10  2:17 Andrew Cagney
2003-01-10  6:45 ` Andrew Cagney
2003-01-10 21:33   ` Daniel Jacobowitz [this message]
2003-01-11 18:14     ` Andrew Cagney
2003-01-11 18:34       ` Daniel Jacobowitz
2003-01-11 20:42         ` Andrew Cagney
2003-01-11 20:54           ` 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=20030110213400.GA8623@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.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