https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64878
--- Comment #10 from ctice at gcc dot gnu.org ---
Author: ctice
Date: Fri Apr 8 17:09:09 2016
New Revision: 234832
URL: https://gcc.gnu.org/viewcvs?rev=234832=gcc=rev
Log:
Unify changes with Android's GCC 4.9 compiler.
Add the following
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64878
--- Comment #9 from Yvan Roux yroux at gcc dot gnu.org ---
Author: yroux
Date: Thu Mar 5 14:28:05 2015
New Revision: 221216
URL: https://gcc.gnu.org/viewcvs?rev=221216root=gccview=rev
Log:
gcc/
2015-03-05 Yvan Roux yvan.r...@linaro.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64878
--- Comment #7 from Sebastian Pop spop at gcc dot gnu.org ---
Author: spop
Date: Fri Feb 6 21:08:13 2015
New Revision: 220491
URL: https://gcc.gnu.org/viewcvs?rev=220491root=gccview=rev
Log:
PR 64878: do not jump thread across more than one
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64878
Jakub Jelinek jakub at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64878
--- Comment #6 from Jakub Jelinek jakub at gcc dot gnu.org ---
(In reply to Sebastian Pop from comment #5)
Created attachment 34665 [details]
fix
Thanks for working on this. s/accross/across/. Please mail it to gcc-patches
once you test it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64878
--- Comment #5 from Sebastian Pop spop at gcc dot gnu.org ---
Created attachment 34665
-- https://gcc.gnu.org/bugzilla/attachment.cgi?id=34665action=edit
fix
The problem is that we jump thread twice across the loop latch:
first, from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64878
--- Comment #4 from Sebastian Pop spop at gcc dot gnu.org ---
The problem is in the recursion step of
fsm_find_control_statement_thread_paths:
for (i = 0; i gimple_phi_num_args (phi); i++)
{
tree arg = gimple_phi_arg_def (phi, i);
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64878
Jakub Jelinek jakub at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64878
Jakub Jelinek jakub at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64878
--- Comment #1 from Sebastian Pop spop at gcc dot gnu.org ---
It fails with -O2 --param max-fsm-thread-paths=10 and does not fail with 9.
This is the thread that generates wrong code:
Registering FSM jump thread: (102, 6) incoming edge; (5,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64878
--- Comment #2 from Sebastian Pop spop at gcc dot gnu.org ---
Jump threading is called twice as two separate passes, the miscompiled jump
thread during the first invocation is:
Registering FSM jump thread: (10, 114) incoming edge; (4, 93)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64878
--- Comment #3 from Sebastian Pop spop at gcc dot gnu.org ---
-fdbg-cnt=registered_jump_thread:44 passes
-fdbg-cnt=registered_jump_thread:45 fails
So this is the jump thread that produces the wrong code:
Registering FSM jump thread: (10, 114)
12 matches
Mail list logo
