From: Richard Henderson <rth@redhat.com>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: [patch] generic simd support
Date: Sun, 16 Jun 2002 10:59:00 -0000 [thread overview]
Message-ID: <20020616105909.A23074@redhat.com> (raw)
In-Reply-To: <20020616091000.GA15592@redhat.com>; from aldyh@redhat.com on Sun, Jun 16, 2002 at 07:10:00PM +1000
On Sun, Jun 16, 2002 at 07:10:00PM +1000, Aldy Hernandez wrote:
> * gcc.c-torture/execute/simd-1.c: New.
>
> * gcc.dg/simd-1.c: New.
>
> * doc/extend.texi (Vector Extensions): Document that we can
> specify simd types not specifically supported by the hardware.
> Document that simd types can be used as function arguments.
> Document that signness does make a difference in SIMD types.
> Misc cleanups and revisions to the "vector extensions" section.
>
> * simplify-rtx.c (simplify_subreg): Simplify subregs of vector
> constants.
>
> * expr.c (vector_mode_valid_p): New.
>
> * expr.h: Add vector_mode_valid_p.
>
> * defaults.h (VECTOR_MODE_SUPPORTED_P): Set default.
>
> * c-common.c (type_for_mode): Always build vector nodes regardless
> of VECTOR_MODE_SUPPORTED_P.
> (handle_mode_attribute): Error if we can't emulate a nonexisting
> vector mode.
> (handle_vector_size_attribute): Same.
>
> * optabs.c (expand_binop): Open-code vector operations.
> (expand_unop): Open-code vector unops.
> (expand_vector_binop): New.
> (expand_vector_unop): New.
>
> * c-typeck.c (build_binary_op): Allow vectors in binops.
> Allow vectors in conditional operatiors.
> (build_unary_op): Allow vectors in unary minus.
>
> * config/rs6000/rs6000.h (ALTIVEC_VECTOR_MODE): Conditionalize on
> TARGET_ALTIVEC.
Ok.
r~
prev parent reply other threads:[~2002-06-16 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 17:45 Aldy Hernandez
2002-05-22 14:09 ` Daniel Egger
2002-05-30 15:42 ` Richard Henderson
2002-06-16 2:10 ` Aldy Hernandez
2002-06-16 10:59 ` Richard Henderson [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=20020616105909.A23074@redhat.com \
--to=rth@redhat.com \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.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