[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Compiling Programs to Windows Stand-Alone Executables
From: |
Joe Koski |
Subject: |
Re: Compiling Programs to Windows Stand-Alone Executables |
Date: |
Wed, 01 Jun 2005 17:36:27 -0600 |
User-agent: |
Microsoft-Entourage/11.1.0.040913 |
on 6/1/05 4:57 PM, David Bateman at address@hidden wrote:
>> On my short tests it was slower than native interpreter :(
>
>
> Only the do-until loops are optimized and only for a couple of
> operations. The rest uses generic code... It was more a proof of concept
> that would be easy enough to expand to include other loops, operations
> and types, while still allowing untreated code to be used... So I'm not
> surprised you didn't see any speed improvement...
>
> D.
>
>
Could there also be an overhead associated with compiling that eliminates
the advantage for quickly executed code, but as the time spent executing the
routine increases, the compiled code starts executing faster than its
interpreted equivalent? How quickly that break point occurs would determine
the true usefulness of the approach.
Joe
-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.
Octave's home on the web: http://www.octave.org
How to fund new projects: http://www.octave.org/funding.html
Subscription information: http://www.octave.org/archive.html
-------------------------------------------------------------