From: Linus Torvalds <torvalds@linux-foundation.org>
To: Esben Nielsen <nielsen.esben@googlemail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Con Kolivas <kernel@kolivas.org>, Nick Piggin <npiggin@suse.de>,
Mike Galbraith <efault@gmx.de>,
Arjan van de Ven <arjan@infradead.org>,
Peter Williams <pwil3058@bigpond.net.au>,
Thomas Gleixner <tglx@linutronix.de>,
caglar@pardus.org.tr, Willy Tarreau <w@1wt.eu>,
Gene Heskett <gene.heskett@gmail.com>, Mark Lord <lkml@rtr.ca>,
Zach Carter <linux@zachcarter.com>,
buddabrod <buddabrod@gmail.com>
Subject: Re: [patch] CFS scheduler, -v8
Date: Mon, 7 May 2007 09:28:32 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0705070921390.3802@woody.linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705071159530.14011@frodo.shire>
On Mon, 7 May 2007, Esben Nielsen wrote:
>
> What is (long)(a-b) ? I have tried to look it up in the C99 standeard but I
> can't find it. Maybe it is in the referred LIA-1 standeard, which I can't find
> with google.
I don't worry about non-2's-complement machines (they don't exist, and
likely won't exist in the future either).
So I worry about compilers rewriting my code.
So "(long)(a-b) < 0" (with "a" and "b" being unsigned long) is basically a
portable way of testing the high bit of the result.
> I think the best would be to use "a-b > ULONG_MAX/2" when you mean "a<b" as
> that should be completely portable.
That certainly works too, but the difference is irrelevant, since Linux is
unlikely to work on insane machines anyway (ie we do make a lot of other
assumptions about the architecture, being two's-complement is the least of
those).
So you basically shouldn't worry about hardware: everybody is pretty much
the same. You should worry about *compilers* - that's where the
differences show up.
So "(long)(a-b)" may be "implementation defined" (but since
implementations are all 2's complement, we don't care), but a signed
"(a-b)" that over/overflows is *undefined*, and that is much worse because
it means that the compiler can do some funky stuff, and _that_ is a real
practical worry.
And no, I also don't worry about porting Linux to 18-bit machines, or to
ternary CPU's.
Linus
next prev parent reply other threads:[~2007-05-07 16:30 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 21:22 Ingo Molnar
2007-05-02 2:57 ` Ting Yang
2007-05-02 5:10 ` Willy Tarreau
2007-05-02 5:30 ` William Lee Irwin III
2007-05-02 10:05 ` Bill Huey
2007-05-02 10:27 ` Ingo Molnar
2007-05-02 17:36 ` Srivatsa Vaddagiri
2007-05-02 17:48 ` William Lee Irwin III
2007-05-02 18:15 ` Ingo Molnar
2007-05-02 18:56 ` William Lee Irwin III
2007-05-02 19:12 ` Ingo Molnar
2007-05-02 19:42 ` William Lee Irwin III
2007-05-03 2:48 ` Ting Yang
2007-05-03 3:18 ` Ting Yang
2007-05-03 10:19 ` Bill Huey
2007-05-02 23:41 ` Ting Yang
2007-05-02 18:42 ` Li, Tong N
2007-05-02 19:10 ` William Lee Irwin III
2007-05-03 3:07 ` Ting Yang
2007-05-03 8:50 ` Ingo Molnar
2007-05-03 14:26 ` Srivatsa Vaddagiri
2007-05-03 15:19 ` Ting Yang
2007-05-03 15:02 ` Ting Yang
2007-05-02 6:37 ` Mike Galbraith
2007-05-02 6:45 ` Ingo Molnar
2007-05-02 8:03 ` Gene Heskett
2007-05-02 8:12 ` Mike Galbraith
2007-05-02 8:48 ` Gene Heskett
2007-05-02 8:13 ` Ingo Molnar
2007-05-02 8:51 ` Gene Heskett
2007-05-02 7:59 ` Mike Galbraith
2007-05-02 8:11 ` Gene Heskett
2007-05-02 10:40 ` Ingo Molnar
2007-05-02 9:08 ` Balbir Singh
2007-05-02 10:05 ` Ingo Molnar
2007-05-02 10:59 ` Balbir Singh
2007-05-02 11:17 ` Ingo Molnar
2007-05-05 8:31 ` Esben Nielsen
2007-05-05 17:44 ` Linus Torvalds
2007-05-06 8:29 ` Ingo Molnar
2007-05-06 8:36 ` Willy Tarreau
2007-05-06 8:52 ` Ingo Molnar
2007-05-06 17:45 ` Linus Torvalds
2007-05-07 11:30 ` Esben Nielsen
2007-05-07 15:55 ` Ingo Molnar
2007-05-07 16:11 ` Linus Torvalds
2007-05-08 0:35 ` Peter Williams
2007-05-08 9:05 ` Esben Nielsen
2007-05-09 0:01 ` Peter Williams
2007-05-10 13:09 ` Pavel Machek
2007-05-11 16:50 ` Linus Torvalds
2007-05-11 19:18 ` Pavel Machek
2007-05-11 19:37 ` Willy Tarreau
2007-05-11 20:53 ` Kevin Bowling
2007-05-07 11:09 ` Esben Nielsen
2007-05-07 16:28 ` Linus Torvalds [this message]
2007-05-07 18:39 ` Johannes Stezenbach
2007-05-07 18:55 ` Linus Torvalds
2007-05-08 7:34 ` Esben Nielsen
2007-05-08 9:54 ` Johannes Stezenbach
2007-05-08 10:27 ` Esben Nielsen
2007-05-08 5:36 ` Matt Mackall
2007-05-02 12:58 ` Mark Lord
2007-05-02 12:58 ` Vegard Nossum
2007-05-02 16:41 ` Ingo Molnar
2007-05-03 8:20 Zoltan Boszormenyi
2007-05-03 13:02 ` Ingo Molnar
2007-05-03 13:29 ` Damien Wyart
2007-05-03 14:53 ` Srivatsa Vaddagiri
2007-05-03 15:53 ` William Lee Irwin III
2007-05-03 18:44 ` Li, Tong N
2007-05-03 19:52 ` William Lee Irwin III
2007-05-07 14:22 ` Srivatsa Vaddagiri
2007-05-07 20:54 ` Li, Tong N
2007-05-07 0:04 ` Bill Davidsen
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=alpine.LFD.0.98.0705070921390.3802@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=buddabrod@gmail.com \
--cc=caglar@pardus.org.tr \
--cc=efault@gmx.de \
--cc=gene.heskett@gmail.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@zachcarter.com \
--cc=lkml@rtr.ca \
--cc=mingo@elte.hu \
--cc=nielsen.esben@googlemail.com \
--cc=npiggin@suse.de \
--cc=pwil3058@bigpond.net.au \
--cc=tglx@linutronix.de \
--cc=w@1wt.eu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®