public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "irar at il dot ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/37491] [4.4 Regression] Revision 140257 causes vectorizer tests failures
Date: Mon, 15 Sep 2008 09:13:00 -0000	[thread overview]
Message-ID: <20080915091142.17259.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37491-682@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from irar at il dot ibm dot com  2008-09-15 09:11 -------
(In reply to comment #6)

> 
> I see vect_create_data_ref_ptr is getting the type to use passed
> in case of stores and this is TREE_TYPE (vec_oprnd) - is vec_oprnd
> the lhs or the rhs?  It looks like it is the rhs which may explain
> the ICE for PR37385, 

It's the other way around in PR37385 - it ICEs if we use the type of lhs.

> I can try to have a look here, but I'm not exactly familiar with
> the code (thanks for the pointers ;)), so I'd appreciate if you
> try to figure out what it takes to fix vect_create_data_ref_ptr or
> its caller.

Sure, I never meant to ask you to look into the vectorizer code. I only gave
you the pointers because I thought you asked. Fixing the vectorizer code is not
a problem. The problem is I don't really understand what we should generate. 

For scalar store *x = y we create vector store *vect_x = vect_y. The type of
vect_x must be "vector type_of_x", right? This will cause the ICE in pr 37385,
so we must check something to prevent it. AFAIU, the ICE is because the lhs and
the element type of rhs do not alias. Testing "vector type_of_x" and
"type_of_y" for alias does the job. But this prevents vectorization of
vectorize2.c (vector int and long int do not alias)...

Thanks a lot for your help,
Ira


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37491


  parent reply	other threads:[~2008-09-15  9:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12  0:33 [Bug middle-end/37491] New: " hjl dot tools at gmail dot com
2008-09-13 12:42 ` [Bug middle-end/37491] " rguenth at gcc dot gnu dot org
2008-09-14  7:02 ` irar at il dot ibm dot com
2008-09-14  9:33 ` rguenth at gcc dot gnu dot org
2008-09-14 10:05 ` irar at il dot ibm dot com
2008-09-14 10:37 ` rguenther at suse dot de
2008-09-14 12:06 ` irar at il dot ibm dot com
2008-09-14 12:54 ` rguenther at suse dot de
2008-09-15  9:13 ` irar at il dot ibm dot com [this message]
2008-09-15  9:24 ` rguenther at suse dot de
2008-09-15  9:36 ` irar at il dot ibm dot com
2008-09-15  9:40 ` rguenther at suse dot de
2008-09-17 10:11 ` rguenth at gcc dot gnu dot org
2008-09-17 11:44 ` rguenth at gcc dot gnu dot org
2008-09-17 11:45 ` rguenth at gcc dot gnu dot org
2008-09-22  9:25 ` irar at il dot ibm dot com
2008-09-22 10:08 ` rguenth at gcc dot gnu dot org
2008-09-22 10:34 ` irar at il dot ibm dot com
2008-09-22 11:16 ` rguenther at suse dot de
2008-09-22 11:49 ` rguenth at gcc dot gnu dot org
2008-09-22 12:33 ` irar at il dot ibm dot com
2008-09-22 12:42 ` irar at il dot ibm dot com
2008-09-30 10:39 ` rguenth at gcc dot gnu dot org

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=20080915091142.17259.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).