public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Dmitry Plotnikov <dplotnikov@ispras.ru>
Cc: gcc-patches@gcc.gnu.org, IRAR@il.ibm.com, rearnsha@arm.com, dm@ispras.ru
Subject: Re: [PATCH] Vectorize conversions directly
Date: Fri, 10 Dec 2010 16:05:00 -0000	[thread overview]
Message-ID: <4D024B37.80908@redhat.com> (raw)
In-Reply-To: <4D00D204.3080300@ispras.ru>

On 12/09/2010 04:56 AM, Dmitry Plotnikov wrote:
> 2010-12-09  Dmitry Plotnikov  <dplotnikov@ispras.ru>
> 
> gcc/
> 	* tree-cfg.c (verify_gimple_assign_unary): Allow vector conversions.
> 	* tree-vect-stmts.c (supportable_convert_operation): New function.
> 	  (vectorizable_conversion): Call it.  Change condition and behavior 
> 	  for NONE modifier case.
> 	* tree-vectorizer.h (supportable_convert_operation): New prototype.
> 	* tree.h (VECTOR_INTEGER_TYPE_P): New macro.
> 
> gcc/config/arm/
> 	* neon.md (floatv2siv2sf2): New.
> 	  (floatunsv2siv2sf2): New.
> 	  (fix_truncv2sfv2si2): New.
> 	  (fix_truncunsv2sfv2si2): New.
> 	  (floatv4siv4sf2): New.
> 	  (floatunsv4siv4sf2): New.
> 	  (fix_truncv4sfv4si2): New.
> 	  (fix_truncunsv4sfv4si2): New.
> 	
> gcc/testsuite/
> 	* gcc.target/arm/vect-vcvt.c: New test.
> 	* gcc.target/arm/vect-vcvtq.c: New test.

Patch looks generally ok; I'll let another Richard approve the ARM bits.

> +  /* First check if we can done conversion directly.  */

 ... if we can do the conversion ...

> +++ b/gcc/testsuite/gcc.target/arm/neon/vect-vcvt.c
> @@ -0,0 +1,28 @@
> +/* { dg-do compile } */
> +/* { dg-options "-O2 -mfpu=neon -mfloat-abi=softfp -ftree-vectorize -fdump-tree-vect-details" } */

Missing dg-final bits for this test.

Neither test requires stdarg.h; remove it.


r~

  reply	other threads:[~2010-12-10 15:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24 16:09 Dmitry Plotnikov
2010-11-24 16:35 ` Dmitry Plotnikov
2010-11-27  4:12   ` Richard Henderson
2010-12-09 14:06     ` Dmitry Plotnikov
2010-12-10 16:05       ` Richard Henderson [this message]
     [not found]         ` <4EA04B20.1090009@ispras.ru>
2011-10-20 17:46           ` [PATCH][PING] " Richard Henderson
2011-10-21 12:23             ` Ramana Radhakrishnan
2011-10-24  9:25           ` Dmitry Plotnikov
2011-10-24 14:39             ` Joseph S. Myers
2011-10-24 15:48               ` Ramana Radhakrishnan
2011-10-24 17:11                 ` Joseph S. Myers
2011-10-28  8:51                   ` Dmitry Plotnikov
2011-10-28 15:25                     ` Richard Henderson
2011-11-08  9:16                     ` [PATCH][PING^2] " Dmitry Plotnikov
2011-11-22 13:40                       ` [PATCH][PING^3] " Dmitry Plotnikov
2011-11-22 14:04                     ` [PATCH][PING] " Ramana Radhakrishnan
2011-11-26 15:15                       ` Ira Rosen
2011-12-22 13:27                         ` Dmitry Plotnikov
2011-12-22 13:48                           ` Richard Earnshaw
2010-11-24 17:28 ` [PATCH] " Richard Guenther
2010-11-25 18:25 ` Ramana Radhakrishnan

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=4D024B37.80908@redhat.com \
    --to=rth@redhat.com \
    --cc=IRAR@il.ibm.com \
    --cc=dm@ispras.ru \
    --cc=dplotnikov@ispras.ru \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rearnsha@arm.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).