public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/45720] [4.6 regression] Revision 164367 miscompiled SPEC CPU 2K Date: Thu, 21 Oct 2010 10:04:00 -0000 [thread overview] Message-ID: <20101021100400.43yvEFe55aOpKR4fZ7usemi0KhzewZz5dx71Ip-HGYk@z> (raw) In-Reply-To: <bug-45720-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45720 --- Comment #2 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> 2010-10-03 05:41:44 UTC --- Author: hjl Date: Sun Oct 3 05:39:32 2010 New Revision: 164914 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=164914 Log: Disallow negative steps in vectorizer. gcc/ 2010-10-02 H.J. Lu <hongjiu.lu@intel.com> PR tree-optimization/45720 PR tree-optimization/45764 * tree-vect-data-refs.c (vect_analyze_data_ref_access): Don't accept backwards consecutive accesses. (vect_create_data_ref_ptr): Disallow negative steps. * tree-vect-stmts.c (vectorizable_store): Allow negative steps. (perm_mask_for_reverse): Removed. (reverse_vec_elements): Likewise. (vectorizable_load): Don't hanle negative steps. gcc/testsuite/ 2010-10-02 H.J. Lu <hongjiu.lu@intel.com> PR tree-optimization/45720 PR tree-optimization/45764 * g++.dg/torture/pr45764.C: New. * gcc.dg/vect/pr43432.c: Xfail. * gcc.dg/vect/vect-114.c: Likewise. * gcc.dg/vect/vect-15.c: Likewise. Added: trunk/gcc/testsuite/g++.dg/torture/pr45764.C Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gcc.dg/vect/pr43432.c trunk/gcc/testsuite/gcc.dg/vect/vect-114.c trunk/gcc/testsuite/gcc.dg/vect/vect-15.c trunk/gcc/tree-vect-data-refs.c trunk/gcc/tree-vect-stmts.c --- Comment #3 from Richard Guenther <rguenth at gcc dot gnu.org> 2010-10-21 10:03:49 UTC --- Likely a dup of PR45764 which has all the analysis.
next prev parent reply other threads:[~2010-10-21 10:04 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-45720-4@http.gcc.gnu.org/bugzilla/> 2010-09-29 19:33 ` rguenth at gcc dot gnu.org 2010-10-21 10:04 ` rguenth at gcc dot gnu.org [this message] 2010-10-21 16:28 ` hjl.tools at gmail dot com 2010-10-22 0:29 ` hjl.tools at gmail dot com 2010-10-22 4:29 ` vladimir.a.kharchenko at intel dot com 2010-10-22 9:00 ` rguenth at gcc dot gnu.org 2010-10-22 10:16 ` vladimir.a.kharchenko at intel dot com 2010-10-22 11:21 ` ubizjak at gmail dot com 2010-10-22 12:26 ` rguenth at gcc dot gnu.org 2010-10-22 13:22 ` rguenth at gcc dot gnu.org 2010-10-22 14:45 ` rguenth at gcc dot gnu.org 2010-10-23 2:09 ` hjl.tools at gmail dot com 2010-09-18 15:56 [Bug middle-end/45720] New: " hjl dot tools at gmail dot com 2010-09-18 16:29 ` [Bug middle-end/45720] " hjl dot tools at gmail dot com 2010-09-18 18:46 ` 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=20101021100400.43yvEFe55aOpKR4fZ7usemi0KhzewZz5dx71Ip-HGYk@z \ --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: linkBe 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).