[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1154050195.44c968932df8d@portal.student.luth.se>
Date: Fri, 28 Jul 2006 03:29:55 +0200
From: ricknu-0@...dent.ltu.se
To: Nicholas Miell <nmiell@...cast.net>
Cc: Arnd Bergmann <arnd.bergmann@...ibm.com>,
linux-kernel@...r.kernel.org, Andrew Morton <akpm@...l.org>,
Jeff Garzik <jeff@...zik.org>,
Alexey Dobriyan <adobriyan@...il.com>,
Vadim Lobanov <vlobanov@...akeasy.net>,
Jan Engelhardt <jengelh@...ux01.gwdg.de>,
Shorty Porty <getshorty_@...mail.com>,
Peter Williams <pwil3058@...pond.net.au>,
Michael Buesch <mb@...sch.de>,
Pekka Enberg <penberg@...helsinki.fi>,
Stefan Richter <stefanr@...6.in-berlin.de>, larsbj@...lik.net,
Paul Jackson <pj@....com>
Subject: Re: [RFC][PATCH] A generic boolean (version 6)
Citerar Nicholas Miell <nmiell@...cast.net>:
> On Thu, 2006-07-27 at 21:55 +0200, ricknu-0@...dent.ltu.se wrote:
> > Citerar Nicholas Miell <nmiell@...cast.net>:
> >
> > > If _Bool does end up in the user-kernel ABI, be advised that validating
> > > them will be tricky ("b == true || b == false" or "!!b" won't work), and
> >
> > Why would !!b not work?
> > I don't think it should end up in the ABI (at least, not yet). Just asking
> > because I'm curious. :)
> >
>
> The compiler knows that "b = !!b;" is a no-op.
In what gcc version? Using 4.0.2 myself and got that if b equals 12 (using a
pointer to add the value to the boolean) then !!b equals 1.
/Richard Knutsson
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists