Re: profile g95
- From: Herman D. Knoble <SkipKnobleLESS@xxxxxxxxxxxxxxx>
- Date: Thu, 28 Sep 2006 08:25:30 -0400
Windows 2000 Resource Kit routine, TimeThis.exe will display
elapsed time for a command. This will be close to the CPU time
if no other apps are running during the timing. It works under
Windows XP.
http://www.microsoft.com/downloads/details.aspx?familyid=913795CD-7026-4143-AE85-1F5E096F9BE0&displaylang=en
If you don't mind doing a time subtract you can write a .bat file
to display elapsed time start and time end for a command:
echo off
rem Set the prompt to the time of day.
prompt $t$g
if exist %1.BAT GOTO CALLIT
echo on
%1 %2 %3 %4 %5 %6 %7 %8 %9
echo off
GOTO WRAPUP
:CALLIT
echo on
CALL %1 %2 %3 %4 %5 %6 %7 %8 %9
echo off
:WRAPUP
rem Restore the usual prompt.
prompt $p$g
On 27 Sep 2006 11:21:49 -0700, beliavsky@xxxxxxx wrote:
-|I use mingw g95 on Windows XP. Is there a profiling tool to measure how
-|CPU time is consumed, or should I just sprinkle calls to the CPU_TIME
-|intrinsic in the code? If there is a tool that works only on Linux, I
-|could profile the code there -- I'd guess that the timings should be
-|similar.
.
- References:
- profile g95
- From: beliavsky
- profile g95
- Prev by Date: Re: comment and IBM xlf
- Next by Date: Re: numeric difference program
- Previous by thread: Re: profile g95
- Next by thread: numeric difference program
- Index(es):
Relevant Pages
|