From: Daniel Jacobowitz <drow@false.org>
To: Girish Shilamkar <girish@linsyssoft.com>
Cc: gdb@sources.redhat.com
Subject: Re: Invalid update to pc in instruction
Date: Tue, 28 Mar 2006 15:20:00 -0000 [thread overview]
Message-ID: <20060328143420.GA30581@nevyn.them.org> (raw)
In-Reply-To: <1143537953.4865.6.camel@krypton>
On Tue, Mar 28, 2006 at 02:55:53PM +0530, Girish Shilamkar wrote:
> 363 in uaccess.h
> Invalid update to pc in instruction
> 0xc00ef530 <memcpy+16>: pld [r1]
> I am using cross gdb-6.4 for Intel PXA270 (armv5l) processor.
> Kindly let me know in what scenario does the error msg "Invalid update
> to pc in instruction" is displayed ?
A quick look in the source would find this message is issued in only
two places:
if (bits (this_instr, 22, 25) == 0
&& bits (this_instr, 4, 7) == 9) /* multiply */
error (_("Invalid update to pc in instruction"));
and
if (bit (this_instr, 22))
error (_("Invalid update to pc in instruction"));
The prologue analyzer thinks that pld [r1] is an instruction which sets
PC, incorrectly. It should be updated.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-03-28 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 14:34 Girish Shilamkar
2006-03-28 15:20 ` Daniel Jacobowitz [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=20060328143420.GA30581@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=girish@linsyssoft.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