From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com, rearnsha@arm.com
Subject: Re: RFA/ARM: Switch mode when setting PC
Date: Fri, 16 Jan 2004 05:43:00 -0000 [thread overview]
Message-ID: <40077A12.5040306@gnu.org> (raw)
In-Reply-To: <20040116035402.GA3215@nevyn.them.org>
> This patch fixes several failures in virtfunc.exp for arm-sim/-mthumb. The
> problem is that the non-virtual thunk for pDe->vg() is emitted in ARM mode
> and called via _call_via_r2. But the rest of the program is Thumb mode, and
> nothing tells the simulator (or target; I haven't tested this on hardware
> yet but I expect the same result) to switch to ARM. So it gets very
> confused.
>
> This is somewhat suboptimal in that if you want, for some reason, to call
> something marked as an ARM function with Thumb mode enabled you will have to
> set $ps yourself _after_ setting $pc. I think it's still a good idea,
> though. OK?
(sorry, but I don't understand that paragraph - doesn't that code set
the $ps after setting the $pc?)
The ari contains this yellow card:
write pc
Replace write_pc() with get_frame_base_address or get_frame_id; at
present the inferior function call code still uses this when doing a
DECR_PC_AFTER_BREAK
the concern is with the way write_pc is being called to perform two
different operations:
- decrement the pc just after the target stops
Arrrg!
- jump to a specific address
As with an inferior function call or jump.
I think it would be better to have two methods so that it's clear that
this case only applies when doing a jump.
Andrew
next prev parent reply other threads:[~2004-01-16 5:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 3:54 Daniel Jacobowitz
2004-01-16 5:43 ` Andrew Cagney [this message]
2004-01-16 14:10 ` Daniel Jacobowitz
2004-01-16 14:15 ` Richard Earnshaw
2004-01-16 14:26 ` Daniel Jacobowitz
2004-01-16 14:34 ` Richard Earnshaw
2004-01-16 14:41 ` Daniel Jacobowitz
2004-01-16 15:00 ` Richard Earnshaw
2004-01-16 15:56 ` Daniel Jacobowitz
2004-01-16 16:55 ` Richard Earnshaw
2004-01-16 17:11 ` Daniel Jacobowitz
2004-01-16 17:28 ` Richard Earnshaw
2004-01-16 19:12 ` Andrew Cagney
2004-01-16 17:32 ` Daniel Jacobowitz
2004-01-16 18:57 ` Andrew Cagney
2004-01-17 4:58 ` Daniel Jacobowitz
2004-01-17 10:49 ` Richard Earnshaw
2004-01-17 16:36 ` Andrew Cagney
2004-01-17 16:12 ` Andrew Cagney
2004-01-17 18:54 ` Daniel Jacobowitz
2004-01-17 21:59 ` Daniel Jacobowitz
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=40077A12.5040306@gnu.org \
--to=cagney@gnu.org \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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