public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <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: Sun, 14 Sep 2008 09:33:00 -0000	[thread overview]
Message-ID: <20080914093235.13436.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37491-682@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from rguenth at gcc dot gnu dot org  2008-09-14 09:32 -------
I don't follow.  For vectorize2.c we have

    b[i] = lrint (a[i]);

where we should be able to vectorize this using lrint vectorization and
a scalar long -> int conversion (which is a no-op on i686 and should be
vectorized on x86_64).  There is no aliasing issue involved here.

But yes, the testcase should be changed to actually check something more
meaningful than one or more cvtpd2dq instructions.

Same for vectorize3.c.

The loop in pr36493.c should also be vectorizable, there isn't any alias
problem there.

Oh well, I guess the alias check logic in the vectorizer is still bogus.


-- 


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


  parent reply	other threads:[~2008-09-14  9:33 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 [this message]
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
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=20080914093235.13436.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).