From: Aldy Hernandez <aldyh@redhat.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb@sources.redhat.com, ezannoni@redhat.com
Subject: Re: [RFC] Tests for vector types?
Date: Mon, 20 May 2002 20:50:00 -0000 [thread overview]
Message-ID: <20020521034951.GE416@redhat.com> (raw)
In-Reply-To: <3CE99939.649D5415@redhat.com>
> > i have some patches i'm polishing up to provide just that-- any
> > SIMD type (say V4SI) regardless of if the hardware supports it. this
> > will make it easier to write generic tests.
>
> That's what I mean -- I'm thinking, support for the vector type
> really has nothing to do with the architecture. The vector type
> is just an array that is passed by value, rather than by reference.
> You don't have to have a special register to do that.
give me a week or two. the patches are done but need documentation.
aldy
prev parent reply other threads:[~2002-05-21 3:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 17:18 Michael Snyder
2002-05-20 17:32 ` Aldy Hernandez
2002-05-20 17:52 ` Elena Zannoni
2002-05-20 18:02 ` Michael Snyder
2002-05-20 20:50 ` Aldy Hernandez [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=20020521034951.GE416@redhat.com \
--to=aldyh@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=msnyder@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