Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751769AbaB0U0u (ORCPT ); Thu, 27 Feb 2014 15:26:50 -0500 Received: from terminus.zytor.com ([198.137.202.10]:60005 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750942AbaB0U0t (ORCPT ); Thu, 27 Feb 2014 15:26:49 -0500 User-Agent: K-9 Mail for Android In-Reply-To: References: <1393462087.24588.50.camel@joe-AO722> <530E8C2E.7080307@zytor.com> <1393466619.24588.65.camel@joe-AO722> <20140227022857.GC23659@thin> <1393469594.24588.71.camel@joe-AO722> <20140227025845.GA25145@thin> <530EB103.5070406@zytor.com> <1393472326.24588.82.camel@joe-AO722> <20140227040050.GA8449@nicira.com> <530EBCED.9020705@zytor.com> <20140227042636.GA9592@nicira.com> <530EBFC7.9030309@zytor.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: [PATCH V2] sparse: Allow override of sizeof(bool) warning From: "H. Peter Anvin" Date: Thu, 27 Feb 2014 12:26:14 -0800 To: Christopher Li CC: Ben Pfaff , Joe Perches , Josh Triplett , Linux-Sparse , Linux Kernel Mailing List Message-ID: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I would. On February 27, 2014 12:22:45 PM PST, Christopher Li wrote: >On Wed, Feb 26, 2014 at 8:32 PM, H. Peter Anvin wrote: >> >> Quite frankly, this is silly in my opinion, *and* it is not >guaranteed >> by C either (read about "trap representations"). >>> >> Anything that moves data around in a generic fashion. It can be as >> simple as: >> >> memcpy(foo, bar, sizeof *foo); > >OK. I get it nobody wants a sizeof(_Bool) warning. > >I am going to apply this patch. > >Should we change the default to off then? > >Thanks. > >Chris -- Sent from my mobile phone. Please pardon brevity and lack of formatting. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/