[Lazarus] Timing of all compiler options on slow machines

[waldo kitty]

On 8/22/2013 07:42, Sven Barth wrote:
> Am 21.08.2013 17:45, schrieb Sven Barth:
>> Maybe I'll need to test this on my mobile development computer as well (800
>> MHz Intel Stealy processor, 1 GB RAM, Windows 7) ^^
> I've written a simple application that uses TProcess to start "fpc -i" and "fpc
> -h" and reads it standard and error output. The "fpc" executable can be passed
> as parameter.
>
> On my above mentioned 800 MHz system "fpc -i" takes ~445ms and "fpc -h" ~540ms
> for a 2.6.2 fpc.exe. If I now use a 2.6.2 ppc386.exe (which is called by
> fpc.exe) the time is ~240ms and ~315ms respectively.
>
> I've attached the lpr if someone wants to test him-/herself.

saved as processtest.lpr... opened laz and opened a project... pointed to 
processtest.lpr and chose 'Application' when laz asked what kind of project... 
was 'Application' the proper project to choose?


also, i edited line 49 where the value of 'exe' is set to 'fpc' to put in the 
complete path and filename since there is no apparent path search or extension...

   exe := 'X:\freepascal\fpc\trunk\bin\i386-win32\fpc.exe'


running gives me the following in a popup box...


   Process processtest raised exception class 'RunError(103)'.

    In file 'processtest.lpr' at line 39:
   Writeln('Duration: ', FormatDateTime('hh:nn:ss.zzz', Now - start));


clicking [Continue] gives me this in another popup box...


   Project processtest raised exception class 'EInOutError' with message:
   File not open

    In file 'processtest.lpr' at line 39:
   Writeln('Duration: ', FormatDateTime('hh:nn:ss.zzz', Now - start));


clicking [Continue] gives me this in a final popup box...


   An unhandled exception occurred at $004017E4:
   EInOutError: File not open
     $004017E4 EXECUTEPROCESS, line 39 of processtest.lpr
     $004018EA main, line 52 of processtest.lpr


thinking that it might be a path related problem, i copied fpc.exe and 
ppc386.exe into the same directory as this processtest project... then i was 
able to see processtest start fpc and fpc attempted to start ppp386.exe but i 
got the same outputs as above...

-- 
NOTE: No off-list assistance is given without prior approval.
       Please keep mailing list traffic on the list unless
       private contact is specifically requested and granted.