Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: "David S. Miller" <davem@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Improve Sparc epilogue analysis
Date: Thu, 25 Apr 2002 14:11:00 -0000	[thread overview]
Message-ID: <3CC86E14.F795FFE5@redhat.com> (raw)
In-Reply-To: <20020424.175238.00378500.davem@redhat.com>

"David S. Miller" wrote:
> 
>    From: Michael Snyder <msnyder@redhat.com>
>    Date: Wed, 24 Apr 2002 17:36:02 -0700
> 
>    "David S. Miller" wrote:
>    > I'd like to ask that you re-review this change, given this, please.
> 
>    The part that's mentioned in the changelog entry is OK, except
>    you can remove sparc_skip_prologue_frameless_p (and say so in
>    the changelog) rather than rewrite it.
> 
> Wait a second, how can I remove sparc_skip_prologue_frameless_p
> when it isn't even there anymore? :-)
> 
> What exists is "sparc_prologue_frameless_p" which is a boolean.
> That is what replaces the functionality for what I removed
> (sparc_skip_prologue_frameless_p, SKIP_PROLOGUE_FRAMELESS_P,
> et al.).
> 
> I think you're still a little confused on the current state of
> the tree.

That comment was unnecessary, thank you.

Whether the function is in or out, it is wrong as written, 
or at the least you have to justify why you have changed
the behavior.

The existing function returns TRUE if and only if the input
address is equal to the address returned by examine_prologue, 
which in this case will be the address of one of a small set
of specific instructions (eg. a SAVE or an add sp).

Your function, in the presence of symbols, will return TRUE
if and only if the input address is equal to the last instruction
in the line (presumably of the prologue).  This is a change.
I don't know whether it was intentional or not, but you can't
make it without explaining it.


  reply	other threads:[~2002-04-25 21:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-20  0:31 David S. Miller
2002-04-23 12:32 ` Michael Snyder
2002-04-24  0:09   ` David S. Miller
2002-04-24 16:27     ` Michael Snyder
2002-04-24 17:15       ` David S. Miller
2002-04-24 17:48         ` Michael Snyder
2002-04-24 17:54           ` David S. Miller
2002-04-24 18:02           ` David S. Miller
2002-04-25 14:11             ` Michael Snyder [this message]
2002-04-25 18:33               ` David S. Miller
2002-04-24 18:15           ` David S. Miller
2002-04-24 22:10             ` Eli Zaretskii
2002-04-25 11:44               ` Michael Snyder
2002-04-25 14:16             ` Michael Snyder
2002-04-25 18:38               ` David S. Miller
2002-04-24 19:10           ` David S. Miller
2002-04-25 14:25             ` Michael Snyder

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=3CC86E14.F795FFE5@redhat.com \
    --to=msnyder@redhat.com \
    --cc=davem@redhat.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