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 tree-optimization/64365] Predictive commoning after loop vectorization produces incorrect code. Date: Wed, 14 Jan 2015 09:00:00 -0000 [thread overview] Message-ID: <bug-64365-4-u0EghPJ0vi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64365-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64365 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |wrong-code Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2015-01-14 Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Can you provide an executable testcase that abort()s when miscompiled and terminates successfully if not? Thus something suitable for the testsuite? That also makes it possible to bisect to a commit that broke this. A hint may be <bb 6>: + _6 = MEM[(int *)in_7(D) + 24B(OVF)]; goto <bb 4>; that appears in the pcom dump.
next prev parent reply other threads:[~2015-01-14 9:00 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-20 0:25 [Bug tree-optimization/64365] New: " congh at google dot com 2015-01-13 22:15 ` [Bug tree-optimization/64365] " congh at google dot com 2015-01-14 9:00 ` rguenth at gcc dot gnu.org [this message] 2015-01-14 12:14 ` rguenth at gcc dot gnu.org 2015-01-14 12:15 ` [Bug tree-optimization/64365] [5 Regression] " rguenth at gcc dot gnu.org 2015-01-14 12:36 ` jakub at gcc dot gnu.org 2015-01-14 12:44 ` [Bug tree-optimization/64365] [4.9/5 " rguenth at gcc dot gnu.org 2015-01-14 13:27 ` rguenth at gcc dot gnu.org 2015-01-15 8:41 ` rguenth at gcc dot gnu.org 2015-01-15 10:31 ` [Bug tree-optimization/64365] [4.9 " rguenth at gcc dot gnu.org 2015-01-15 18:15 ` congh at google dot com 2015-01-22 22:59 ` brooks at gcc dot gnu.org 2015-01-23 9:13 ` rguenther at suse dot de 2015-01-29 19:58 ` brooks at gcc dot gnu.org 2015-01-30 3:25 ` brooks at gcc dot gnu.org 2015-02-19 14:14 ` rguenth at gcc dot gnu.org 2015-02-19 14:14 ` rguenth 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-64365-4-u0EghPJ0vi@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).