From: Ben Pfaff <blp@nicira.com>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] evaluate: Allow sizeof(_Bool) to succeed.
Date: Mon, 9 May 2011 13:02:31 -0700 [thread overview]
Message-ID: <20110509200231.GG2971@nicira.com> (raw)
In-Reply-To: <BANLkTikHwADf5Kv5=rQosKcNjsMYM-28wQ@mail.gmail.com>
On Sat, May 07, 2011 at 01:37:04PM -0700, Christopher Li wrote:
> On Wed, May 4, 2011 at 4:39 PM, Ben Pfaff <blp@nicira.com> wrote:
> > Without this commit, sizeof(_Bool) provokes an error with "cannot size
> > expression" because _Bool is a 1-bit type and thus not a multiple of a full
> > byte in size. ?But sizeof(_Bool) is valid C that should evaluate to 1, so
> > this commit fixes the problem and adds a regression test.
>
> The sizeof _Bool is implementation define. Gcc make sizeof(_Bool) as 1.
> I modify your patch to issue an warning. Applied and pushed.
>
> The incremental change follows. Please check that works for you or not.
Thank you for applying my patch. It does work for me, in the sense
that I get a warning instead of an error now, but I'm not so happy to
get any diagnostic at all. Is there some reason why sizeof(_Bool)
warrants a warning when, say, sizeof(long) does not? After all, both
sizes are implementation defined.
Thanks,
Ben.
next prev parent reply other threads:[~2011-05-09 20:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 23:39 [PATCH] evaluate: Allow sizeof(_Bool) to succeed Ben Pfaff
2011-05-07 20:37 ` Christopher Li
2011-05-09 20:02 ` Ben Pfaff [this message]
2011-05-09 20:31 ` Christopher Li
2011-05-09 20:49 ` Ben Pfaff
2011-05-12 0:09 ` Christopher Li
2011-05-12 20:48 ` Ben Pfaff
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=20110509200231.GG2971@nicira.com \
--to=blp@nicira.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
/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.