Jamie McCracken wrote: >>> well thats soemthing you should add to your to do list. Automatic >>> inlining can deliver a signifcant performance improvement especially >>> as delphi uses a lot of one line procedures to set property values. A >>> fucntion call adds quite a bit of overhead (around 10+ clock cycles >>> at a guess) >> >> >> >> But inlining doesn't help if the one line procedures are virtual methods. > > > Well thats not a limitation on other languages. EG for Java the get/set > property methods were identified as causing one of the biggest > performance hits and thats why now almost every JIT/AOT inlines them
They are basically interpreted languages which suck anyways: http://shootout.alioth.debian.org/benchmark.php?test=all&lang=gcc&lang2=java&sort=fullcpu > automatically (the same also applies to Mono). Even against FPC it doesn't help java much: http://shootout.alioth.debian.org/benchmark.php?test=all&lang=java&lang2=fpascal&sort=fullcpu > > jamie. > > _______________________________________________ > fpc-devel maillist - fpc-devel@lists.freepascal.org > http://lists.freepascal.org/mailman/listinfo/fpc-devel _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
