Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Altivec ABI patches
Date: Thu, 02 May 2002 00:22:00 -0000	[thread overview]
Message-ID: <npwuun10ak.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <npvga73kxv.fsf@zwingli.cygnus.com>

Jim Blandy <jimb@redhat.com> writes:
> Elena Zannoni <ezannoni@redhat.com> writes:
> > Jim Blandy writes:
> >  > 
> >  > I don't see anything here that prevents vectors from being coerced to
> >  > pointers to their first element.  Isn't there some change needed in
> >  > evaluate_subexp_with_coercion?
> > 
> > You mean value_arg_coerce()?
> 
> Err, ... yeah, that's what I meant.  :)

Wait, no.  If `v' is a vector variable, and the user types `print v +
2', that should be an error, right?  But somehow it'll get promoted to
a pointer to its first element.  value_add calls COERCE_NUMBER, which
calls COERCE_ARRAY.  I think that's what you need to fix.  Note that
value_subscript already handles arrays specially --- it doesn't depend
on C's array coercion --- so it should continue to work.  I think.

You may have already done this, but I'd grep for TYPE_CODE_ARRAY and
make sure each case is handled properly.


      reply	other threads:[~2002-05-02  7:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26 13:45 Elena Zannoni
2002-04-26 16:02 ` Kevin Buettner
2002-04-26 18:45   ` Elena Zannoni
2002-04-27  1:08     ` Kevin Buettner
2002-04-27 12:12       ` David Edelsohn
2002-04-29  8:40       ` Elena Zannoni
2002-04-29 12:45         ` Jim Blandy
2002-04-29 13:31           ` Elena Zannoni
2002-05-01  9:13             ` Jim Blandy
2002-05-02  0:22               ` Jim Blandy [this message]

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=npwuun10ak.fsf@zwingli.cygnus.com \
    --to=jimb@redhat.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@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