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/43901] [4.6 Regression] FAIL: gcc.c-torture/compile/pr42196-2.c
Date: Wed, 05 May 2010 09:02:00 -0000	[thread overview]
Message-ID: <20100505090228.16008.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43901-682@http.gcc.gnu.org/bugzilla/>



------- Comment #14 from irar at il dot ibm dot com  2010-05-05 09:02 -------

> It tries to get a _vector_ type of the same size.  In theory each
> vectorization method can choose whatever vector size suits them
> most (as for external defs they need to build up a vector of equivalent
> elements anyway).  So with AVX we can do V4DF -> V4SF vectorization,
> if the double is an external def the vectorization method could choose
> to create a vector with double size.  But the reasonable default for
> now is th force a same-sized vector type as that is what the vectorizer
> was tested for until now (well, until I get the followup patch cleaned
> up and posted again).

OK, thanks for the explanation.

> 
> So yes, if we can return false we should probably do so instead of
> asserting (maybe assert that if we are supposed to create vectorized
> stmts and thus cannot fail that we indeed have a vector type here).

I'll prepare a patch.

Thanks,
Ira

> 
> Richard.
> 


-- 

irar at il dot ibm dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |irar at il dot ibm dot com
                   |dot org                     |
             Status|NEW                         |ASSIGNED
   Last reconfirmed|2010-05-02 10:44:22         |2010-05-05 09:02:26
               date|                            |


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


  parent reply	other threads:[~2010-05-05  9:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 19:19 [Bug middle-end/43901] New: " hjl dot tools at gmail dot com
2010-04-27  5:53 ` [Bug middle-end/43901] " irar at il dot ibm dot com
2010-04-27  9:36 ` rguenth at gcc dot gnu dot org
2010-04-27 13:07 ` hjl dot tools at gmail dot com
2010-04-27 13:11 ` rguenth at gcc dot gnu dot org
2010-05-02  5:51 ` irar at il dot ibm dot com
2010-05-02 10:44 ` ubizjak at gmail dot com
2010-05-02 10:46 ` ubizjak at gmail dot com
2010-05-02 10:50 ` ubizjak at gmail dot com
2010-05-02 11:02 ` ubizjak at gmail dot com
2010-05-02 11:08 ` irar at il dot ibm dot com
2010-05-02 12:12 ` irar at il dot ibm dot com
2010-05-03 11:17 ` rguenth at gcc dot gnu dot org
2010-05-03 11:17 ` rguenther at suse dot de
2010-05-03 12:31 ` irar at il dot ibm dot com
2010-05-03 12:35 ` rguenther at suse dot de
2010-05-05  9:02 ` irar at il dot ibm dot com [this message]
2010-05-06  6:43 ` irar at gcc dot gnu dot org
2010-05-10  8:18 ` irar at il dot ibm dot com

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=20100505090228.16008.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).