From: Joel Brobecker <brobecker@gnat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/mips] merge mips32_skip_prologue into mips32_scan_prologue
Date: Thu, 14 Oct 2004 22:37:00 -0000 [thread overview]
Message-ID: <20041014223715.GI1375@gnat.com> (raw)
In-Reply-To: <416C49B8.9040906@gnu.org>
> >2004-10-11 Joel Brobecker <brobecker@gnat.com>
> >
> > * mips-tdep.c (mips32_scan_prologue): Merge code from
> > mips32_skip_prologue. Now return the address of the first
> > instruction past the function prologue.
> > (mips32_skip_prologue): Remove. No longer necessary.
> > (mips16_skip_prologue): Add parameter end_pc instead of
> > computing it.
> > (mips_skip_prologue): Compute the upper limit for the
> > prologue scanning. Update call to mips16_skip_prologue.
> > Replace call to mips32_skip_prologue by call to
> > mips32_scan_prologue.
> Yes, and also ok to follow-on patches at this incremental level.
Thanks! This one has been committed. I will work on the mips16
equivalent, and then look at the couple of items raised in this
thread.
--
Joel
prev parent reply other threads:[~2004-10-14 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 5:51 Joel Brobecker
2004-10-12 21:17 ` Andrew Cagney
2004-10-14 22:37 ` Joel Brobecker [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=20041014223715.GI1375@gnat.com \
--to=brobecker@gnat.com \
--cc=cagney@gnu.org \
--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