public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Dorit Naishlos <DORIT@il.ibm.com>
Cc: Chao-ying Fu <fu@mips.com>,
	gcc-patches@gcc.gnu.org, "Stephens,
	Nigel" <nigel@mercury.mips.com>,
	"Thekkath, Radhika" <radhika@mercury.mips.com>,
	Richard Sandiford <rsandifo@redhat.com>,
	"Uhler, Mike" <uhler@mercury.mips.com>,
	Jim Wilson <wilson@specifixinc.com>
Subject: Re: [patch] extend.texi MIPS PS/3D Support
Date: Tue, 28 Sep 2004 00:41:00 -0000	[thread overview]
Message-ID: <20040927234323.GA31317@redhat.com> (raw)
In-Reply-To: <OF41FFD841.792CD1E9-ONC2256F1C.007F85CC-C2256F1C.008116E2@il.ibm.com>

On Tue, Sep 28, 2004 at 01:30:00AM +0200, Dorit Naishlos wrote:
> Maybe the problem is here (in get_vectype_for_scalar_type):
> 
>   vectype = build_vector_type (scalar_type, nunits);
>   if (TYPE_MODE (vectype) == BLKmode)
>     return NULL_TREE;
> 
> Maybe the vectype that is built has a mode other than BLKmode, although
> it's not supported by the target?

Yes, e.g. V4QI may be represented with SImode.  But that's fine,
since the vectorizer may be able to optimize data movement loops
with no other vector support in the target.  (E.g. if target and
destination are alignable.)

The real problem is that you're pulling out SImode and deciding
that add_optab[SImode] is the vector addition operation.


r~

  reply	other threads:[~2004-09-27 23:43 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-23 18:02 Fu, Chao-Ying
2004-09-24 12:17 ` Dorit Naishlos
2004-09-24 21:35   ` Chao-ying Fu
2004-09-25 10:53     ` Richard Sandiford
2004-09-27 23:32       ` Chao-ying Fu
2004-09-28  0:32         ` Dorit Naishlos
2004-09-28  0:41           ` Richard Henderson [this message]
2004-09-28 14:07             ` Dorit Naishlos
2004-09-28 14:08               ` Paolo Bonzini
2004-09-29 11:41                 ` Paolo Bonzini
2004-09-29 17:33                   ` Richard Henderson
2004-09-29 23:39                   ` Dorit Naishlos
2004-10-11 22:48                   ` [patch] vectorizer: fix handling of non VECTOR_MODE_P vectypes Dorit Naishlos
2004-10-12  0:40                     ` Richard Henderson
2004-10-12 12:54                       ` Dorit Naishlos
2004-10-12 16:37                         ` Richard Henderson
2004-10-12 18:21                           ` Dorit Naishlos
2004-10-12 20:49                             ` James A. Morrison
2004-10-13  8:46                               ` Dorit Naishlos
2004-10-13 19:18                         ` Richard Henderson
2004-09-28 19:35               ` [patch] extend.texi MIPS PS/3D Support Chao-ying Fu
2004-09-28 23:04               ` Richard Henderson
  -- strict thread matches above, loose matches on Subject: below --
2004-09-24  0:12 Fu, Chao-Ying
2004-10-02 11:35 ` Richard Sandiford
2004-10-05  7:15   ` Richard Sandiford
2004-09-22 22:13 Fu, Chao-Ying
2004-09-22 22:05 Fu, Chao-Ying
2004-09-23 17:40 ` Richard Sandiford
2004-09-22  0:21 Fu, Chao-Ying
2004-09-22  2:46 ` Giovanni Bajo
2004-09-22  3:14   ` Devang Patel
2004-09-22 11:24     ` Dorit Naishlos
2004-09-22  7:36   ` Richard Sandiford
2004-09-22 11:06   ` Dorit Naishlos
2004-10-26 14:29   ` Gerald Pfeifer
2004-09-22  8:53 ` Richard Sandiford

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=20040927234323.GA31317@redhat.com \
    --to=rth@redhat.com \
    --cc=DORIT@il.ibm.com \
    --cc=fu@mips.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nigel@mercury.mips.com \
    --cc=radhika@mercury.mips.com \
    --cc=rsandifo@redhat.com \
    --cc=uhler@mercury.mips.com \
    --cc=wilson@specifixinc.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).