On Sat, Nov 03, 2001 at 02:03:12AM +, [EMAIL PROTECTED] wrote:
Method2 is broken because it gives erroneous results.
In my original post I presented a small program that
called three different versions of a RDTSC functions
(1,2,2A) and only method 1 gave results that were in any
On Thu, Nov 01, 2001 at 02:54:37PM -0700, John Regehr wrote:
Don't forget to make sure it's __volatile__, elsewise this is the very
epitome of what would produce dodgy results...
Right. So method2 and method2A seem to be broken in multiple ways -
forget you ever saw them. Rather, look
On Thu, Nov 01, 2001 at 02:54:37PM -0700, John Regehr wrote:
Don't forget to make sure it's __volatile__, elsewise this is the very
epitome of what would produce dodgy results...
Right. So method2 and method2A seem to be broken in multiple ways -
forget you ever saw them.
Method2 is broken because it gives erroneous results.
In my original post I presented a small program that
called three different versions of a RDTSC functions
(1,2,2A) and only method 1 gave results that were in any
posssible way correct. Since these are three different
functions, there
On Wed, Oct 31, 2001 at 05:37:18PM -0700, John Regehr wrote:
method1 : 23573589435592- 23573353927542 = 235508050
method2 : 23573353927556- 23573353927556 = 0
method2A : 23573353927607- 23573353927607 = 0
-- also m2_1 - m1_1 = 14
-- and
Don't forget to make sure it's __volatile__, elsewise this is the very
epitome of what would produce dodgy results...
Right. So method2 and method2A seem to be broken in multiple ways -
forget you ever saw them. Rather, look at this page:
There were (at least) three sample implementations of a
C-function to read the Pentium's time-stamp counter. I
originally implemented two and when I discovered a problem
with the results of one, I implemented the third which was
supposed to be an improved version of the second. The
results of
