From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753272Ab1IJF16 (ORCPT ); Sat, 10 Sep 2011 01:27:58 -0400 Received: from mail-pz0-f42.google.com ([209.85.210.42]:46073 "EHLO mail-pz0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750986Ab1IJF14 (ORCPT ); Sat, 10 Sep 2011 01:27:56 -0400 Date: Fri, 9 Sep 2011 22:27:19 -0700 From: Dan Carpenter To: H Hartley Sweeten Cc: linux-sparse@vger.kernel.org, Linux Kernel Subject: Re: improper sparse warnings in linux kernel build? Message-ID: <20110910052719.GC4807@mwanda> References: <201109091541.28395.hartleys@visionengravers.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201109091541.28395.hartleys@visionengravers.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 09, 2011 at 03:41:28PM -0700, H Hartley Sweeten wrote: > I'm not really sure what the DEFINE_PER_CPU macro expands to so I'm not > sure if the 'static' in front is actually getting used or if sparse is just > confused. > > Is this an actual problem in the linux kernel or is sparse just getting > tripped up by the DEFINE_PER_CPU macro? > I don't have a kernel git archive handy, but probably sparse is correct. Do a "make arch/x86/kernel/cpu/mcheck/mce_intel.i" and run sparse on the .i file to find the line number that complains. regards, dan carpenter