Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [cagney_convert-20030606-branch] Add value to REGISTER_TO_VALUE et.al.
Date: Mon, 09 Jun 2003 14:20:00 -0000	[thread overview]
Message-ID: <3EE497BC.6050601@redhat.com> (raw)
In-Reply-To: <200306090938.h599cg5F000458@elgar.kettenis.dyndns.org>

>    Date: Sun, 08 Jun 2003 18:10:29 -0400
>    From: Andrew Cagney <ac131313@redhat.com>
> 
>    Ok,  I've changed the branch to:
> 
>    > The ``obvious'' interfaces were:
>    > 
>    > register_to_value (frame, regnum, type, buffer)
>    > value_to_register (frame, regnum, type, buffer)
>    > 
>    > but that tripped up on something (now what ...?).  Dig dig.
>    > Notice how, to preserve existing behavior,
>    > legacy_register_to_value saves the location based on what
>    > frame_register returns.  We'd have to switch to
>    > lval_reg_frame_relative.
> 
>    And this time it appears to be going better.  I'll try to attribute it 
>    to VALUE_FRAME_ID and the use of put_frame_register (neither of which I 
>    did last time).
> 
> Andrew, the attached fixes writing values into registers.  OK to check
> this in on the branch?

Yep, thanks!

Andrew


> Index: ChangeLog
> from  Mark Kettenis  <kettenis@gnu.org>
> 
> 	* valops.c (value_assign): Assign contents of FROMVAL instead of
> 	TOVAL.
> 
> Index: valops.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/valops.c,v
> retrieving revision 1.110.2.2
> diff -u -p -r1.110.2.2 valops.c
> --- valops.c 8 Jun 2003 22:14:42 -0000 1.110.2.2
> +++ valops.c 9 Jun 2003 09:02:27 -0000
> @@ -588,13 +588,12 @@ value_assign (struct value *toval, struc
>  	  error ("Value being assigned to is no longer active.");
>  	
>  	if (VALUE_LVAL (toval) == lval_reg_frame_relative
> -	    && CONVERT_REGISTER_P (VALUE_FRAME_REGNUM (toval),
> -				   VALUE_TYPE (toval)))
> +	    && CONVERT_REGISTER_P (VALUE_FRAME_REGNUM (toval), type))
>  	  {
>  	    /* If TOVAL is a special machine register requiring
>  	       conversion of program values to a special raw format.  */
>  	    VALUE_TO_REGISTER (frame, VALUE_FRAME_REGNUM (toval),
> -			       VALUE_TYPE (toval), VALUE_CONTENTS (toval));
> +			       type, VALUE_CONTENTS (fromval));
>  	  }
>  	else
>  	  {
> 



  reply	other threads:[~2003-06-09 14:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-04 19:38 [wip/rfc] Merge REGISTER_TO_VALUE and REGISTER_TO_TYPE Andrew Cagney
2003-06-04 21:45 ` Mark Kettenis
2003-06-04 23:05   ` Andrew Cagney
2003-06-06 18:12   ` [cagney_convert-20030606-branch] Add value to REGISTER_TO_VALUE et.al Andrew Cagney
2003-06-08 16:43     ` Mark Kettenis
2003-06-08 17:15       ` Andrew Cagney
2003-06-08 22:11         ` Andrew Cagney
2003-06-08 22:51           ` Mark Kettenis
2003-06-09  0:22             ` Andrew Cagney
2003-06-09  9:35               ` Mark Kettenis
2003-06-09 14:38                 ` Andrew Cagney
2003-06-09  9:38           ` Mark Kettenis
2003-06-09 14:20             ` Andrew Cagney [this message]
2003-06-09 17:43               ` Mark Kettenis
2003-06-09 10:26           ` Mark Kettenis

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=3EE497BC.6050601@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    /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