Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA/ARM: Switch mode when setting PC
Date: Fri, 16 Jan 2004 18:57:00 -0000	[thread overview]
Message-ID: <40083424.1000102@gnu.org> (raw)
In-Reply-To: <20040116173235.GA7498@nevyn.them.org>

> On Fri, Jan 16, 2004 at 09:10:40AM -0500, Daniel Jacobowitz wrote:
> 
>> > 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.
> 
>> 
>> Well, it'd be better to rip out the current DECR_PC_AFTER_BREAK and
>> handle it completely within the four (roughly) affected targets,
>> thereby removing the overloading of write_pc.  IMVHO.

It's been on everyones wish list for too long.  Last time I tried I got 
bogged down due to a lack of ia32 doco - that's now been fixed though.

> Hi Andrew,
> 
> Is this patch OK (write_pc isn't deprecated yet!)?  Cleaning up the
> existing DECR_PC_AFTER_BREAK handling is going to be a touchy job, and
> I don't really want to try it today :)  I'll try to look into it later,
> though.

I was suggesting "two methods so that it's clear that this case only 
applies when doing a jump".  This won't involve anything like 
deprecating /removing decr_pc_after_break _+ write_pc but will involve 
the addition of a new method like:
	set_resume_address (arch, targ or tpid or regs)
that could somehow default to a legacy call to write_pc.  Significantly, 
this will avoid making the changes conditional on the elimination of 
decr-pc (your concern).

Why is this better?  It clearly separates the [apparently] legetimate 
resume case from the decr-pc case.  This in turn opens the way for the 
deprecate / delete decr-pc "write_pc" code while at the same time 
ensuring that the work can't break the arm.

enjoy,
Andrew



  reply	other threads:[~2004-01-16 18:57 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
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 [this message]
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=40083424.1000102@gnu.org \
    --to=cagney@gnu.org \
    --cc=drow@mvista.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