From: "Emilio G. Cota" <cota@braap.org>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH v2] Define __CHAR_BIT__
Date: Tue, 28 Jan 2014 16:38:10 -0500 [thread overview]
Message-ID: <20140128213810.GA27471@flamenco.cs.columbia.edu> (raw)
In-Reply-To: <1389216762-10884-1-git-send-email-cota@braap.org>
On Wed, Jan 08, 2014 at 16:32:42 -0500, Emilio G. Cota wrote:
> From: "Emilio G. Cota" <cota@braap.org>
>
> gcc defines __CHAR_BIT__ as a pre-defined macro.
>
> Define __CHAR_BIT__ in sparse so that code that needs it (e.g. code
> using CHAR_BIT from limits.h) does not generate false warnings.
>
> Signed-off-by: Emilio G. Cota <cota@braap.org>
Haven't seen any activity for this v2 since it was sent on
Jan 08--please take a look.
Thanks,
Emilio
prev parent reply other threads:[~2014-01-28 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 5:46 [PATCH] Define __CHAR_BIT__ Emilio G. Cota
2013-12-21 17:20 ` Christopher Li
2014-01-08 21:32 ` [PATCH v2] " Emilio G. Cota
2014-01-28 21:38 ` Emilio G. Cota [this message]
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=20140128213810.GA27471@flamenco.cs.columbia.edu \
--to=cota@braap.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).