From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luc Van Oostenryck Subject: Re: sparse with 4.10? Date: Sat, 16 Sep 2017 16:33:45 +0200 Message-ID: <20170916143343.p32j3uw5rvk4hxp5@ltop.local> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-wm0-f51.google.com ([74.125.82.51]:49128 "EHLO mail-wm0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751253AbdIPOdt (ORCPT ); Sat, 16 Sep 2017 10:33:49 -0400 Received: by mail-wm0-f51.google.com with SMTP id r68so13788770wmg.3 for ; Sat, 16 Sep 2017 07:33:48 -0700 (PDT) Content-Disposition: inline In-Reply-To: Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: "Jason A. Donenfeld" Cc: Christopher Li , Linux-Sparse On Sat, Sep 16, 2017 at 02:25:18PM +0200, Jason A. Donenfeld wrote: > Hey guys, > > Sorry for the delay. I finally produced an extremely minimal test case > that can reproduce this bug. Please see the attached tarball. Hit > make, and you'll see the error: > > ./include/linux/mm.h:1766:47: warning: unknown expression (14 0) > ./include/linux/mm.h:1767:16: warning: call with no type! Thanks, I can now reproduce this. It's quite strange. It's related to the fact that you include mm.h via the '-include' flag. If you include it with '#include' (as it should be), there is no problem. Same when trying with the result of the preprocessing. But all three should have the same effect. The error message itself has somethng to do with the type 'pmd_t' but again I don't see anything wrong there and I suppose it's because of the point above. I'll need to investigate this a bit more. -- Luc Van Oostenryck