From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: Don't try to take address of SIMD vectors
Date: Sat, 26 Mar 2005 22:38:00 -0000 [thread overview]
Message-ID: <20050326223856.GA1151@nevyn.them.org> (raw)
In-Reply-To: <vt2isbrqwrq.fsf@zenia.home>
On Tue, Aug 10, 2004 at 02:26:17AM -0500, Jim Blandy wrote:
>
> This is, in some sense, a followup to:
>
> http://sources.redhat.com/ml/gdb-patches/2002-05/msg00027.html
>
> No regressions on i686-pc-linux-gnu or powerpc-unknown-linux-gnu;
> fixes vector subscripting on PowerPC E500 SIMD vectors.
>
> 2004-08-09 Jim Blandy <jimb@redhat.com>
>
> * eval.c (evaluate_subexp_with_coercion): Don't try to produce a
> pointer to the value's first element if it's a SIMD vector value,
> not an ordinary array.
Hi Jim,
I see that this patch was never checked in. I can't convince myself
from the above that it's necessary; if you still want it, could you
show some examples? Bonus points if they fit in the testsuite.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-26 22:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 7:29 Jim Blandy
2005-03-26 22:38 ` Daniel Jacobowitz [this message]
2005-03-29 17:37 ` Jim Blandy
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=20050326223856.GA1151@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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