[Bug tree-optimization/25623] jump threading messes up "incoming frequencies" for some BBs

2021-08-08 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25623 Andrew Pinski changed: What|Removed |Added Last reconfirmed|2006-03-02 12:57:12 |2021-8-8 Known to fail|

[Bug tree-optimization/25623] jump threading messes up "incoming frequencies" for some BBs

2006-03-10 Thread pinskia at gcc dot gnu dot org
--- Comment #5 from pinskia at gcc dot gnu dot org 2006-03-11 05:05 --- Actually looking at this again, I am starting to think cfg cleanup is causing this and not jump threading really. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added

[Bug tree-optimization/25623] jump threading messes up "incoming frequencies" for some BBs

2006-03-02 Thread rguenth at gcc dot gnu dot org
--- Comment #4 from rguenth at gcc dot gnu dot org 2006-03-02 13:00 --- 4.1.0 has also after dom2: Invalid sum of incoming frequencies 673, should be 21 :; __builtin_abort (); Invalid sum of incoming frequencies 9327, should be 9979 :; return; 4.0.2 has even different mismatched f

[Bug tree-optimization/25623] jump threading messes up "incoming frequencies" for some BBs

2006-03-02 Thread rguenth at gcc dot gnu dot org
--- Comment #3 from rguenth at gcc dot gnu dot org 2006-03-02 12:57 --- Confirmed. It's dom2 messing up. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added

[Bug tree-optimization/25623] jump threading messes up "incoming frequencies" for some BBs

2006-03-02 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-03-02 12:53 --- This still happens as of today. with the C testcase from comment #1, we get: Invalid sum of incoming frequencies 894, should be 9 :; __builtin_abort (); Invalid sum of incoming frequencies 9106, should be 9991 :