Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964953AbVI0POf (ORCPT ); Tue, 27 Sep 2005 11:14:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964969AbVI0POf (ORCPT ); Tue, 27 Sep 2005 11:14:35 -0400 Received: from smtpout.mac.com ([17.250.248.73]:27384 "EHLO smtpout.mac.com") by vger.kernel.org with ESMTP id S964953AbVI0POe (ORCPT ); Tue, 27 Sep 2005 11:14:34 -0400 In-Reply-To: <20050927071025.GS7992@ftp.linux.org.uk> References: <20050927.151301.189720995.takata.hirokazu@renesas.com> <20050927071025.GS7992@ftp.linux.org.uk> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: Hirokazu Takata , torvalds@odsl.org, linux-kernel@vger.kernel.org, sam@ravnborg.org Content-Transfer-Encoding: 7bit From: Kyle Moffett Subject: Re: [PATCH] m32r: set CHECKFLAGS properly Date: Tue, 27 Sep 2005 11:13:44 -0400 To: Al Viro X-Mailer: Apple Mail (2.734) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1050 Lines: 35 On Sep 27, 2005, at 03:10:25, Al Viro wrote: > You do realize that this way sparse will get neither? It does not > pick predefined symbols from gcc; thus the -D, etc. How about sticking this in some global Makefile somewhere? This will give sparse the same list of defines that GCC uses: CHECKFLAGS += $(shell echo | gcc -E - -dM | sed -re 's/^#define +([^ ] +) +(.*)$/-D\1=\2/g') Or you could do this: include/linux/checkerdefines.h: echo | gcc -E - -dM >$@ And in linux/stddef.h or linux/compiler.h or something do: #if defined(__CHECKER__) and not defined(_LINUX_CHECKERDEFINES_H) # define _LINUX_CHECKERDEFINES_H 1 # include #endif Cheers, Kyle Moffett -- Q: Why do programmers confuse Halloween and Christmas? A: Because OCT 31 == DEC 25. - 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/