I ran a quick profile with this patch and it eliminated a couple of
divisions (calls to __divi64 reduced from 4 to 2 in my test setup. your
mileage may vary) which was good for 493 instructions. Still have 3 __divu64
and 2 __divi64 calls. The three __divu64 calls are in the gettimeofday() CRT
From: Bill Stoddard [mailto:[EMAIL PROTECTED]
I ran a quick profile with this patch and it eliminated a couple of
divisions (calls to __divi64 reduced from 4 to 2 in my test setup.
your
mileage may vary) which was good for 493 instructions. Still have 3
__divu64
and 2 __divi64 calls. The
At 01:33 AM 07/11/2002, William A. Rowe, Jr. wrote:
Ok, attached is the code redone as binary math. I'm tired, could be
any number of major blunders in it, but on first pass, it looked right.
-/** number of microseconds per second */
-#define APR_USEC_PER_SEC APR_TIME_C(100)
+/** number of
Greg Marr wrote:
At 01:33 AM 07/11/2002, William A. Rowe, Jr. wrote:
Ok, attached is the code redone as binary math. I'm tired, could be
any number of major blunders in it, but on first pass, it looked right.
-/** number of microseconds per second */
-#define APR_USEC_PER_SEC
At 10:27 AM 07/11/2002, Jim Jagielski wrote:
Greg Marr wrote:
I keep thinking that APR_USEC_PER_SEC should be (1 20), or now
(1 APR_USEC_BITS) instead of the magical constant. I have no
way
of verifying with a quick glance that 1048576 is really 2^20.
It is :)
Well, yes, I did check it,
On Thu, 2002-07-11 at 06:58, Bill Stoddard wrote:
I ran a quick profile with this patch and it eliminated a couple of
divisions (calls to __divi64 reduced from 4 to 2 in my test setup. your
mileage may vary) which was good for 493 instructions. Still have 3 __divu64
and 2 __divi64 calls. The
At 10:41 AM 7/11/2002, Brian Pane wrote:
On Thu, 2002-07-11 at 06:58, Bill Stoddard wrote:
I ran a quick profile with this patch and it eliminated a couple of
divisions (calls to __divi64 reduced from 4 to 2 in my test setup. your
mileage may vary) which was good for 493 instructions. Still
On Thu, 11 Jul 2002, Greg Marr wrote:
I keep thinking that APR_USEC_PER_SEC should be (1 20), or now
(1 APR_USEC_BITS) instead of the magical constant. I have no way
of verifying with a quick glance that 1048576 is really 2^20.
You don't know your powers of 2? Memorize, Greg, Memorize.
