On Wed, Mar 24, 2021 at 4:49 PM Grr <gebbe...@gmail.com> wrote:
>
> Since afterstart = 0, there should be no loop to optimize out except ONE
> value test
>
> One hundred cycles for that would seem excessive for me
>
> TWENTY THOUSAND CYCLES for a _zero_ loop?!?
>
> Maybe in Java

We didn't see the value of transfer->dev->afterstart.

Could this be exposing a bug elsewhere? E.g., afterstart has a
different value than you expect?

Alternately could it be that afterstart had the correct value but the
task was interrupted during the loop and a big portion of the 20,000
cycles were spent doing something else?

Nathan

Reply via email to