Re: kernel/timer.c: next_timer_interrupt() strange/buggy(?) code (2.6.18-rc1-mm2)

[Michael Buesch <mb@bu3sch.de>]

On Tuesday 18 July 2006 16:50, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 18 Jul 2006 16:29:27 +0200, Michael Buesch said:
> 
> > Continue is equal to:
> > 
> > LOOP {
> > 	/* foo */
> > 	goto continue; /* == continue */
> 	/* What the code actually had: */
>         goto found; /* Note placement of the label *AFTER* end of loop */
> > 	/* foo */
> > continue:
> > } LOOP
> 
> found: /* out of the loop entirely */
> 
> A 'continue' drops you *at* the end of the loop. The 'goto found:' in the
> original code drops you *after* the end of the loop.  One will potentially go
> around for another pass, the other you're *done*.

I did not say something else.
I just wanted to say the sentence
> A 'continue' instead would leave the do/while and then
> drive the i==2 and subsequent 'for' iterations....
is wrong. It would _not_ leave the do/while directly.
It will check condition first and _might_ leave it.

-- 
Greetings Michael.