From: Andrew Cagney <ac131313@cygnus.com>
To: Richard.Earnshaw@arm.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [wip/cagney_regbuf-20020515-branch] Introduce regcache_move()
Date: Sat, 18 May 2002 11:27:00 -0000 [thread overview]
Message-ID: <3CE69D06.4070207@cygnus.com> (raw)
In-Reply-To: <200205181137.MAA28231@cam-mail2.cambridge.arm.com>
> rearnsha@arm.com said:
>
>> Write_register_bytes will then overwrite the raw value in the cache
>> without any regard to the masking operations that should be occuring
>> when updating R15; the CPSR bits in the PC are just clobbered and we
>> are left with a broken value in the R15 register.
>
>
> Actually, this isn't a strict description of what happens (though the
> result is pretty much the same). What really happens is that
> write_register_byte will then call write_register_gen for each register
> that returns a REGISTER_BYTE() address in the same range. The result is
> that write_register_bytes calls
>
> write_register_gen(PC, newval)
> write_register_gen(CPSR, newval)
>
> which is still equally bogus.
Yep, and the second write won't do anything. Code will detect that the
location is already up-to-date and supress the write through.
Feel free to express total disbelief! :-)
REGISTER_BYTE is also on the hit-list.
Andrew
next prev parent reply other threads:[~2002-05-18 18:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 9:36 Andrew Cagney
2002-05-18 4:18 ` Richard Earnshaw
2002-05-18 4:38 ` Richard Earnshaw
2002-05-18 11:27 ` Andrew Cagney [this message]
2002-05-18 12:08 ` Andrew Cagney
2002-05-19 7:47 ` Richard Earnshaw
2002-05-19 8:10 ` Andrew Cagney
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=3CE69D06.4070207@cygnus.com \
--to=ac131313@cygnus.com \
--cc=Richard.Earnshaw@arm.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