From: Michael Snyder <msnyder@redhat.com>
To: Richard.Earnshaw@arm.com
Cc: Michael Snyder <msnyder@cygnus.com>,
gdb-patches@sources.redhat.com, rearnsha@arm.com
Subject: Re: [RFA] arm_scan_prologue: accept strh and strb as well as str
Date: Wed, 08 May 2002 11:33:00 -0000 [thread overview]
Message-ID: <3CD96C75.7D72B96E@redhat.com> (raw)
In-Reply-To: <200205081501.QAA15060@cam-mail2.cambridge.arm.com>
Richard Earnshaw wrote:
>
> >
> > Hi Richard,
> >
> > These are for char and short args, respectively.
> > The more I play with it, the more I want to merge
> > arm_scan and arm_skip into one function. ;-)
> >
> > Michael
> >
> > 2002-04-25 Michael Snyder <msnyder@redhat.com>
> >
> > * arm-tdep.c (arm_scan_prologue): Accept strb r(0123),[r11,#-nn]
> > and strh r(0123),[r11,#-nn] as well as str r(0123),[r11,#-nn].
> > (arm_skip_prologue): Ditto.
> >
>
> OK.
>
> As mentioned before, we should also handle
>
> str{,h,b} r(0123), [sp, #+nn]
>
> in the prologue (for frameless functions).
[sorry for the empty reply]
OK -- I'd be glad to do that. Could you possibly
provide me an example to work from?
arm_scan_prologue is easy, since it accepts prologue instructions
in any order, but arm_skip_prologue imposes an ordering on them.
I would REALLY like to merge these two functions. In fact I started
to, but then got busy with other things.
next prev parent reply other threads:[~2002-05-08 18:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-25 18:30 Michael Snyder
2002-05-08 8:02 ` Richard Earnshaw
2002-05-08 11:32 ` Michael Snyder
2002-05-08 11:33 ` Michael Snyder [this message]
2002-05-08 12:11 ` Richard Earnshaw
2002-05-08 15:36 ` Michael Snyder
2002-05-08 15:41 ` Michael Snyder
2002-05-09 2:20 ` Richard Earnshaw
2002-05-09 11:02 ` Michael Snyder
2002-05-09 2:18 ` Richard Earnshaw
2002-05-09 11:07 ` 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=3CD96C75.7D72B96E@redhat.com \
--to=msnyder@redhat.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@cygnus.com \
--cc=rearnsha@arm.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