------- Comment #3 from pinskia at gcc dot gnu dot org 2006-12-05 19:50 ------- (In reply to comment #2) > Hm. When you mark it as [4.0/4.1 Regression], should FIXED mean "fixed > for 4.0/4.1"?
Because it is hard to fix for 4.0/4.1 as either loop.c is causing this missed optimization or the IR changed slightly to cause the issue. Also 3.4.0 had the same issue so I don't think it is the IR Changing issue. What 4.2.0 and above does is lowers __builtin_expect very early on which helps the code gen and gets rid of the problem of having it around. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30055
