Am 12.07.2011 15:38, schrieb Lin Rongrong: > After another half hour compile with --no-peep option, I sadly found the > same problem. Seems that the peephole optimizer is not the source of error. > > Woody >
While I have no idea what kind of program results in such long compile times using the defaults setting, you might try setting --max-allocs-per-node 1000 or so during bug-hunting to save time. Sometimes it helps even doing a kind of bisect on the --max-allocs-per-node parameter, since there are bugas that will not occour at low values, and when a bug appears e.g. at 102 and above , but not at 101 and below, diffing the asm output using 102 vs. 101 can help finding the exact location in the code that is affected by the bug. Philipp ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
