Take the following simple example loop: void __show_backtrace(void *rw) { while(rw); }
We get invalid warnings in the tree dumps about profiling info being wrong: __show_backtrace (rw) { <L3>:; if (rw_1 != 0B) goto <L0>; else goto <L2>; Invalid sum of incoming frequencies 9879, should be 8900 <L0>:; goto <bb 1> (<L0>); Invalid sum of incoming frequencies 121, should be 1100 <L2>:; return; } I am filing this because for 4.2, I hear that the rtl level profiling info will be coming from the tree level (after loop.c is removed). -- Summary: DOM messes up the profiling info Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org,law at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22401