by "Ignacio G.T." <spamtrap@[EMAIL PROTECTED]
>
Mar 24, 2008 at 04:13 PM
Stargazer escribió:
> ...
>
> A little more testing showed that almost all cycles (2300+) were spent
> at access to a global variable (via ds:[] addressing). Nothing that
> accesses stack memory (push, pop, call, mov) makes a noticeable
> difference. Does anybody have an idea why this happens? I test on
> Celeron 2.8G in protected mode set up for flat model with paging
> disabled.
Just catching flies...: are you sure that no exception code (trap or
whatever, it's a long time since I assembled x86 code) is being called
by your inc instruction? Imagine, for instance, an access violation (bad
GDT)
