From: Andrew Morton <akpm@osdl.org>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: viro@ftp.linux.org.uk, linux-kernel@vger.kernel.org,
aia21@cantab.net, len.brown@intel.com
Subject: Re: [patch 1/1] consolidate TRUE and FALSE
Date: Fri, 17 Mar 2006 14:56:49 -0800 [thread overview]
Message-ID: <20060317145649.4215761c.akpm@osdl.org> (raw)
In-Reply-To: <20060317234311.c5e338f6.xavier.bestel@free.fr>
Xavier Bestel <xavier.bestel@free.fr> wrote:
>
> On Thu, 16 Mar 2006 13:26:39 -0800
> Andrew Morton <akpm@osdl.org> wrote:
>
> > C99 does have boolean support, so the proper thing to do is to start
> > using it - implement stdbool.h, fix up fallout, start fixing subsystems.
> > Given that, and as Greg has fixed up this particular build error I'll drop
> > the patch.
>
> Isn't there a runtime cost converting all "non-false" values to a unique "true" (i.e. converting non-zero values to one) ?
Yes, there will be. If people do wrong things.
> I mean:
>
> bool res = strcmp(string, "whatever");
> if(res)
> something_else();
There's an implicit conversion from integer (-1, 0, 1) to boolean there.
It _should_ require a typecast or, better,
bool res = (strcmp(...) != 0);
But it won't require that - the compiler will just accept it.. A new `gcc
--implement-bools-properly' or perhaps sparse should warn about the above.
(Hopefully the compiler would have the brains to optimise it all away in
this specific example).
But yeah, it's always possible to deoptimise your code.
next prev parent reply other threads:[~2006-03-17 22:54 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 10:01 akpm
2006-03-16 10:28 ` Anton Altaparmakov
2006-03-16 10:42 ` Andrew Morton
2006-03-16 19:55 ` Nicholas Miell
2006-03-16 19:55 ` Jan Engelhardt
2006-03-16 10:36 ` Arjan van de Ven
2006-03-16 16:01 ` Christoph Hellwig
2006-03-16 16:29 ` Randy.Dunlap
2006-03-16 16:30 ` Christoph Hellwig
2006-03-16 16:36 ` Randy.Dunlap
2006-03-16 16:36 ` Christoph Hellwig
2006-03-16 16:42 ` Anton Altaparmakov
2006-03-16 16:50 ` Al Viro
[not found] ` <2c0942db0603160905v26011d8dx1e64967b2eb4deac@mail.gmail.com>
2006-03-16 17:11 ` Al Viro
2006-03-16 18:50 ` Anton Altaparmakov
2006-03-16 18:53 ` Anton Altaparmakov
2006-03-16 19:59 ` Jan Engelhardt
2006-03-16 22:35 ` Anton Altaparmakov
2006-03-16 16:42 ` Randy.Dunlap
2006-03-16 16:39 ` Anton Altaparmakov
2006-03-16 17:41 ` Sam Ravnborg
2006-03-16 18:00 ` Al Viro
2006-03-16 18:12 ` Randy.Dunlap
2006-03-16 18:49 ` Al Viro
2006-03-16 18:58 ` Randy.Dunlap
2006-03-16 18:52 ` Sam Ravnborg
2006-03-16 21:17 ` Valdis.Kletnieks
2006-03-16 21:28 ` Joshua Hudson
2006-03-16 23:53 ` David Wagner
2006-03-16 17:09 ` Xavier Bestel
2006-03-16 16:49 ` Al Viro
2006-03-16 21:26 ` Andrew Morton
2006-03-17 22:43 ` Xavier Bestel
2006-03-17 22:56 ` Andrew Morton [this message]
2006-03-18 21:57 ` Jan Engelhardt
2006-03-19 11:41 ` Xavier Bestel
2006-03-16 17:07 ` Greg KH
2006-03-16 17:13 ` Greg KH
2006-03-20 14:46 ` Richard Knutsson
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=20060317145649.4215761c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=aia21@cantab.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
--cc=xavier.bestel@free.fr \
/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®