From: Richard Earnshaw <rearnsha@arm.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: Richard.Earnshaw@arm.com, Michael Snyder <msnyder@cygnus.com>,
gdb-patches@sources.redhat.com, cagney@redhat.com,
rearnsha@arm.com
Subject: Re: [RFA] arm_skip_prologue: recognize "str r(0123), [r11, #-nn]"
Date: Wed, 24 Apr 2002 02:08:00 -0000 [thread overview]
Message-ID: <200204240907.KAA24952@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Tue, 23 Apr 2002 10:35:31 PDT." <3CC59B63.17E26EBC@redhat.com>
msnyder@redhat.com said:
> I have confirmed that, when there is debug info, these instructions
> are lumped with the prologue.
Ok, then as you suggest, they should be included by the manual prologue
groveller code.
R.
next prev parent reply other threads:[~2002-04-24 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 16:29 Michael Snyder
2002-04-23 2:36 ` Richard Earnshaw
2002-04-23 2:55 ` Richard Earnshaw
2002-04-23 10:47 ` Michael Snyder
2002-04-24 2:08 ` Richard Earnshaw [this message]
2002-04-24 14:23 ` Michael Snyder
2002-04-23 10:46 ` 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=200204240907.KAA24952@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=cagney@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@cygnus.com \
--cc=msnyder@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