From: Michael Buesch <mb@bu3sch.de>
To: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
Cc: keir@xensource.com, Tony Lindgren <tony@atomide.com>,
zach@vmware.com, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: kernel/timer.c: next_timer_interrupt() strange/buggy(?) code (2.6.18-rc1-mm2)
Date: Mon, 17 Jul 2006 21:01:42 +0200 [thread overview]
Message-ID: <200607172101.43252.mb@bu3sch.de> (raw)
In-Reply-To: <20060717185330.GA32264@rhlx01.fht-esslingen.de>
On Monday 17 July 2006 20:53, Andreas Mohr wrote:
> (a "continue" simply continue:s the loop without checking the loop condition
> at the bottom, right?)
I don't think so. Test it. This is no infinite loop:
int main(void)
{
int i = 0;
do {
i++;
continue;
} while (i < 1000);
}
--
Greetings Michael.
next prev parent reply other threads:[~2006-07-17 19:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 18:53 kernel/timer.c: next_timer_interrupt() strange/buggy(?) code (2.6.18-rc1-mm2) Andreas Mohr
2006-07-17 19:01 ` Michael Buesch [this message]
2006-07-17 19:57 ` Valdis.Kletnieks
2006-07-18 1:50 ` Steven Rostedt
2006-07-18 14:29 ` Michael Buesch
2006-07-18 14:50 ` Valdis.Kletnieks
2006-07-18 15:04 ` Michael Buesch
2006-07-17 20:22 ` Andreas Schwab
2006-07-18 1:47 ` [PATCH] fix bad macro param in timer.c (was: kernel/timer.c: next_timer_interrupt() strange/buggy(?) code (2.6.18-rc1-mm2)) Steven Rostedt
2006-07-18 1:59 ` [PATCH] fix bad macro param in timer.c Steven Rostedt
2006-07-18 15:14 ` kernel/timer.c: next_timer_interrupt() strange/buggy(?) code (2.6.18-rc1-mm2) Prakash Punnoor
2006-07-18 16:02 ` offtopic boot parameter notsc [Was: Re: kernel/timer.c: next_timer_interrupt() strange/buggy(?) code (2.6.18-rc1-mm2)] Sergio Monteiro Basto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200607172101.43252.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=keir@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=zach@vmware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.