This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/64365] Predictive commoning after loop vectorization produces incorrect code.
- From: "rguenth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 14 Jan 2015 09:00:02 +0000
- Subject: [Bug tree-optimization/64365] Predictive commoning after loop vectorization produces incorrect code.
- Auto-submitted: auto-generated
- References: <bug-64365-4 at http dot gcc dot gnu dot 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.