public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "meibf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/59651] [4.9 Regression] Vectorizer failing to spot dependence causes incorrect code generation. Date: Fri, 03 Jan 2014 15:41:00 -0000 [thread overview] Message-ID: <bug-59651-4-7CoC9DifGo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59651-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59651 --- Comment #8 from meibf at gcc dot gnu.org --- Author: meibf Date: Fri Jan 3 15:40:57 2014 New Revision: 206319 URL: http://gcc.gnu.org/viewcvs?rev=206319&root=gcc&view=rev Log: 2014-01-03 Bingfeng Mei <bmei@broadcom.com> PR tree-optimization/59651 * tree-vect-loop-manip.c (vect_create_cond_for_alias_checks): Address range for negative step should be added by TYPE_SIZE_UNIT. PR tree-optimization/59651 * gcc.dg/torture/pr59651.c: New test. * gcc.dg/vect/pr59651.c: Ditto. Added: trunk/gcc/testsuite/gcc.dg/torture/pr59651.c trunk/gcc/testsuite/gcc.dg/vect/pr59651.c Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-vect-loop-manip.c
next prev parent reply other threads:[~2014-01-03 15:41 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-31 16:28 [Bug tree-optimization/59651] New: " belagod at gcc dot gnu.org 2013-12-31 16:53 ` [Bug tree-optimization/59651] " bmei at broadcom dot com 2013-12-31 17:12 ` belagod at gcc dot gnu.org 2013-12-31 21:07 ` [Bug tree-optimization/59651] [4.9 Regression] " pinskia at gcc dot gnu.org 2013-12-31 22:42 ` bmei at broadcom dot com 2014-01-01 18:31 ` belagod at gcc dot gnu.org 2014-01-02 11:04 ` bmei at broadcom dot com 2014-01-02 11:37 ` belagod at gcc dot gnu.org 2014-01-03 10:53 ` belagod at gcc dot gnu.org 2014-01-03 15:41 ` meibf at gcc dot gnu.org [this message] 2014-01-04 12:04 ` jakub at gcc dot gnu.org 2014-01-21 14:16 ` mshawcroft at gcc dot gnu.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=bug-59651-4-7CoC9DifGo@http.gcc.gnu.org/bugzilla/ \ --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).