TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
"Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Date:
Mon, 6 Nov 2000 14:45:26 -0800
Reply-To:
Tom Moran <[log in to unmask]>
Subject:
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
Content-Type:
text/plain; charset=us-ascii
Organization:
Decision Aids
From:
Tom Moran <[log in to unmask]>
Parts/Attachments:
text/plain (21 lines)
> Presumably DELAY UNTIL is
> implemented with an
> interrupt. Could there be an overhead of some 10 or more
> microseconds
  I would be astonished if Windows did short delays with interrupts.
From my timings, it takes 4.9 mics just to do the OS call etc for "T :=
Ada.Calendar.Clock" (and since Gnat apparently uses the same (the only)
clock for Real_Time and Calendar, that would be same). Most Windows
calls specify times in milliseconds (though that is often misleading
about actual precision).  The thing that ticks at .8 mics is accessed
via a "QueryPerformanceCounter" call - I don't think they really think
of it as a general purpose clock at all.
> So would be surprising in a
> realtime
> operating system, though it is not surprising in a commercial
> operating
> system.
  My timings are running on Windows 95, which is the latter.
Does any version of Windows actually do timing and interrupts in 1
microsecond?

ATOM RSS1 RSS2