Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@codesourcery.com>
To: Ken Werner <ken@linux.vnet.ibm.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>, gdb-patches@sourceware.org
Subject: Re: [patch] Small fix for assigning values to vectors
Date: Fri, 09 Jul 2010 13:03:00 -0000	[thread overview]
Message-ID: <20100709130308.GR8410@caradoc.them.org> (raw)
In-Reply-To: <201007091238.57599.ken@linux.vnet.ibm.com>

On Fri, Jul 09, 2010 at 12:38:57PM +0200, Ken Werner wrote:
> Ok, the attached patch removes coerce_array call as well. Tested on powerpc64-
> *-linux-gnu and i686-*-linux-gnu, no regressions.

I'm confused.

> @@ -1083,13 +1083,6 @@ value_assign (struct value *toval, struc
>        toval = value_coerce_to_target (toval);
>        fromval = value_cast (type, fromval);
>      }
> -  else
> -    {
> -      /* Coerce arrays and functions to pointers, except for arrays
> -	 which only live in GDB's storage.  */
> -      if (!value_must_coerce_to_target (fromval))
> -	fromval = coerce_array (fromval);
> -    }
>  
>    CHECK_TYPEDEF (type);
>  

I thought we were discussing toval, at the top of the context block;
that's the destination.  It seems to me like we do need to coerce
fromval here.  If this works, maybe somewhere else is coercing it
anyway?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2010-07-09 13:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 13:58 Ken Werner
2010-07-07 17:50 ` Ulrich Weigand
2010-07-07 18:26   ` Daniel Jacobowitz
2010-07-09 10:39     ` Ken Werner
2010-07-09 13:03       ` Daniel Jacobowitz [this message]
2010-07-09 13:16         ` Ulrich Weigand
2010-07-09 13:12       ` Ulrich Weigand
2010-07-10 13:04         ` Ken Werner
2010-07-10 15:39           ` Daniel Jacobowitz
2010-07-10 17:05             ` Ken Werner
2010-07-12 14:55               ` Ulrich Weigand
2010-07-14 14:55                 ` Ken Werner

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=20100709130308.GR8410@caradoc.them.org \
    --to=dan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ken@linux.vnet.ibm.com \
    --cc=uweigand@de.ibm.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