On Saturday 26 February 2005 23:03, Jan Hubicka wrote:
Mark? I would say that there is little risk in this patch corectness wise, might have negative effect on compilation times since we re-start inlining more like we did in old days.
Can we see some timings with and without this patch?
Bootstrap times with checking disabled are the same with and without the patch. To be fair I'll try to pick out tests that likely show sensitive
behavior on inlining decisions.
tramp3d-v3 -O3 compile- and run-times without checking are
compile size run 3.4 1m7s 4421288 51s 4.0 1m2s 4531197 1m57s 4.0 patched 2m39s 5391554 27s 3.4 leafify 1m36s 4539503 34s 4.0 leafify 1m52s 4844784 15s
the testcase is unusual as it runs into our default unit-growth inlining limit. Also -O3 is not exactly the best option for runtime speed, but it will surely show the most effects on compile time wrt inlining due to -finline-functions.
PR8361 -O3 compile times are
3.4 25s 4.0 20s 4.0 patched 31s
ublas4 -O3 from ccfun compile times are
3.4 14s 4.0 16s 4.0 patched 19s
spirit -O3 from ccfun compile times are
3.4 24s 4.0 20s 4.0 patched 26s
In the end we surely want to watch CiSBE and SPEC testers.
Richard.
