[Bug middle-end/49465] [4.7 Regression] Revision 175114 miscompiled 403.gcc in SPEC CPU 2006
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49465 --- Comment #5 from H.J. Lu hjl.tools at gmail dot com 2011-06-23 13:05:29 UTC --- (In reply to comment #3) Fix looking good. Doing a cpu2k6 int test right now. Hi Jeff, can I try your patch on my machine? Thanks.
[Bug middle-end/49465] [4.7 Regression] Revision 175114 miscompiled 403.gcc in SPEC CPU 2006
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49465 Jeffrey A. Law law at redhat dot com changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Comment #8 from Jeffrey A. Law law at redhat dot com 2011-06-23 20:26:57 UTC --- Fixed per patch.
[Bug middle-end/49465] [4.7 Regression] Revision 175114 miscompiled 403.gcc in SPEC CPU 2006
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49465 --- Comment #6 from Jeffrey A. Law law at gcc dot gnu.org 2011-06-23 20:26:10 UTC --- Author: law Date: Thu Jun 23 20:26:07 2011 New Revision: 175351 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=175351 Log: PR middle-end/49465 * tree-ssa-threadupate.c (fix_duplicate_block_edges): Fix condition to detect threading through joiner block. If there was already an edge to the new target, then do not change the PHI nodes. *** fix_duplicate_block_edges (struct redire Modified: trunk/gcc/ChangeLog trunk/gcc/tree-ssa-threadupdate.c
[Bug middle-end/49465] [4.7 Regression] Revision 175114 miscompiled 403.gcc in SPEC CPU 2006
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49465 --- Comment #7 from Jeffrey A. Law law at redhat dot com 2011-06-23 20:26:32 UTC --- Fixed.
[Bug middle-end/49465] [4.7 Regression] Revision 175114 miscompiled 403.gcc in SPEC CPU 2006
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49465 --- Comment #9 from Jeffrey A. Law law at gcc dot gnu.org 2011-06-23 21:26:08 UTC --- Author: law Date: Thu Jun 23 21:26:04 2011 New Revision: 175352 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=175352 Log: PR middle-end/49465 * tree-ssa-threadupate.c (fix_duplicate_block_edges): Fix condition to detect threading through joiner block. If there was already an edge to the new target, then do not change the PHI nodes. Modified: trunk/gcc/ChangeLog
[Bug middle-end/49465] [4.7 Regression] Revision 175114 miscompiled 403.gcc in SPEC CPU 2006
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49465 --- Comment #4 from Yukhin Kirill kirill.yukhin at intel dot com 2011-06-22 04:23:34 UTC --- (In reply to comment #3) Fix looking good. Doing a cpu2k6 int test right now. Jeffrey, could you please share your patch?
[Bug middle-end/49465] [4.7 Regression] Revision 175114 miscompiled 403.gcc in SPEC CPU 2006
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49465 Richard Guenther rguenth at gcc dot gnu.org changed: What|Removed |Added Target Milestone|--- |4.7.0
[Bug middle-end/49465] [4.7 Regression] Revision 175114 miscompiled 403.gcc in SPEC CPU 2006
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49465 --- Comment #1 from Jeffrey A. Law law at redhat dot com 2011-06-20 17:05:56 UTC --- Something goofy happens when we compile loop.c in cpu2k6... Still investigating.
[Bug middle-end/49465] [4.7 Regression] Revision 175114 miscompiled 403.gcc in SPEC CPU 2006
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49465 Jeffrey A. Law law at redhat dot com changed: What|Removed |Added Status|NEW |ASSIGNED AssignedTo|unassigned at gcc dot |law at redhat dot com |gnu.org | --- Comment #2 from Jeffrey A. Law law at redhat dot com 2011-06-20 19:41:43 UTC --- We're mucking up a PHI argument in one particular case... I'm testing a fix.
[Bug middle-end/49465] [4.7 Regression] Revision 175114 miscompiled 403.gcc in SPEC CPU 2006
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49465 --- Comment #3 from Jeffrey A. Law law at redhat dot com 2011-06-20 22:51:17 UTC --- Fix looking good. Doing a cpu2k6 int test right now.
[Bug middle-end/49465] [4.7 Regression] Revision 175114 miscompiled 403.gcc in SPEC CPU 2006
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49465 Jeffrey A. Law law at redhat dot com changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed||2011.06.20 04:52:44 Ever Confirmed|0 |1