|
From: | John W. Eaton |
Subject: | Re: For loop benchmarks between Octave versions |
Date: | Tue, 17 Jun 2014 11:41:47 -0400 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.5.0 |
On 06/17/2014 11:11 AM, Julien Bect wrote:
Le 17/06/2014 16:49, John W. Eaton a écrit :
Does declaring is_active "inline" really make a difference? I'd be surprised if that is not always inlined when the compiler is performing inlining optimizations.Yes, I have tried both, and it does make a (small) difference.
>
The main difference was obtained by calling profiler.is_active directly (2.75 -> 2.26, roughly). The runtime dropped to 2.16 when I added inline.
Consistently?Could you look at the generated assembly code and see whether the "inline" keyword is really needed to get this trivial function to be inlined? What compiler optimization flags are you using?
jwe
[Prev in Thread] | Current Thread | [Next in Thread] |