In message <[EMAIL PROTECTED]>, Dan Nelson cleopede:
>In the last episode (Feb 03), Alfred Perlstein said:
>> * Michal Mertl <[EMAIL PROTECTED]> [020203 08:17] wrote:
>> Not really sure what to make of this, anyone else know how we ought
>> to fix this?
>
>This has actually been an issue for ages,
In the last episode (Feb 03), Alfred Perlstein said:
> * Michal Mertl <[EMAIL PROTECTED]> [020203 08:17] wrote:
> > Several runs of the program take about the same time but the time
> > changes wildly when the executable is called differently.
> >
> > The only thing which I can think of that can
On Sun, 3 Feb 2002 08:59:41 -0800
Alfred Perlstein <[EMAIL PROTECTED]> wrote:
Hi,
> It sure looks like an alignment issue. If you print the address
> of 'i' and 'j' in the attached program you can see for the fast
> case they are aligned to 8 byte boundries, but when it's slow they
> are at an
>
> Several runs of the program take about the same time but the time
> changes wildly when the executable is called differently.
>
> ---
> ./xx/xxx
> 5 s
> xx/xxx
> 9 s
>
> The only thing which I can think of that can be causing this is some
> memory alignment issue.
>
it could also b
* Michal Mertl <[EMAIL PROTECTED]> [020203 08:17] wrote:
> I wrote a simple program which does this:
>
> gettimeofday
> something (takes several seconds)
> gettimeofday
> print time elapsed
>
> Several runs of the program take about the same time but the time
> changes wildly when the executable
I wrote a simple program which does this:
gettimeofday
something (takes several seconds)
gettimeofday
print time elapsed
Several runs of the program take about the same time but the time
changes wildly when the executable is called differently.
---
./xx/xxx
5 s
xx/xxx
9 s
and similar. It h
6 matches
Mail list logo