public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: ken@linux.vnet.ibm.com (Ken Werner)
Cc: dan@codesourcery.com (Daniel Jacobowitz),
	       Ulrich.Weigand@de.ibm.com (Ulrich Weigand),
	gdb-patches@sourceware.org
Subject: Re: [patch] Small fix for assigning values to vectors
Date: Mon, 12 Jul 2010 14:55:00 -0000	[thread overview]
Message-ID: <201007121455.o6CEtale009687@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <201007101905.07082.ken@linux.vnet.ibm.com> from "Ken Werner" at Jul 10, 2010 07:05:06 PM

Ken Werner wrote:

> On Saturday, July 10, 2010 05:39:09 pm Daniel Jacobowitz wrote:
> > On Sat, Jul 10, 2010 at 03:03:53PM +0200, Ken Werner wrote:
> > > But while we are at it. Are there any objections on copying the contents
> > > to the destination instead of creating a pointer?
> > 
> > I think we're going a bit too far now, and maybe we need to figure out
> > what the semantics of internalvars are supposed to be...
> > 
> > With this, IIUC, "set $internalvar = program_array" is going to read
> > the whole array.  Previously, it would decay to a pointer as in C.
> 
> I agree. As I don't have a strong opinion either way on this particular case 
> I'd leave that decision to more experienced GDB developers.

Yes, this is a separate issue; let's leave the behaviour as is for now.
 
> Here is the patch I intended to post where only the call to 
> value_coerce_to_target is omitted and the value_must_coerce_to_target routine 
> returns zero in case of a vector. Tested on powerpc64-*-linux-gnu with no 
> regressions.

> Changelog:
> 
> 2010-07-09  Ken Werner  <ken.werner@de.ibm.com>
> 
> 	* valops.c (value_assign): Do not call to value_coerce_to_target.
> 	(value_must_coerce_to_target): Return 0 in case of TYPE_VECTOR.
> 
> testsuite/ChangeLog:
> 
> 2010-07-09  Ken Werner  <ken.werner@de.ibm.com>
> 
> 	* gdb.arch/altivec-abi.exp: New tests.

This is OK.

I think you should get Write After Approval access to the GDB CVS so that you
can commit your approved patches yourself.  Please apply using this form:
http://sourceware.org/cgi-bin/pdw/ps_form.cgi

Once you get access, please add yourself to the MAINTAINERS file under
the Write After Approval section, and then commit your patch.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com

  reply	other threads:[~2010-07-12 14:55 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
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 [this message]
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=201007121455.o6CEtale009687@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=dan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ken@linux.vnet.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).