From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Emilio G. Cota" Subject: Re: [PATCH v2] Define __CHAR_BIT__ Date: Tue, 28 Jan 2014 16:38:10 -0500 Message-ID: <20140128213810.GA27471@flamenco.cs.columbia.edu> References: <1389216762-10884-1-git-send-email-cota@braap.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from out4-smtp.messagingengine.com ([66.111.4.28]:44049 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755475AbaA1Vj6 (ORCPT ); Tue, 28 Jan 2014 16:39:58 -0500 Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 995FF20C5A for ; Tue, 28 Jan 2014 16:39:57 -0500 (EST) Content-Disposition: inline In-Reply-To: <1389216762-10884-1-git-send-email-cota@braap.org> Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Christopher Li Cc: Linux-Sparse On Wed, Jan 08, 2014 at 16:32:42 -0500, Emilio G. Cota wrote: > From: "Emilio G. Cota" > > 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 Haven't seen any activity for this v2 since it was sent on Jan 08--please take a look. Thanks, Emilio