From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [PATCH] Re: LLVM and PSEUDO_REG/PSEUDO_PHI Date: Mon, 29 Aug 2011 11:14:39 -0400 Message-ID: <4E5BACDF.6050401@garzik.org> References: <4E5495C9.6050207@kernel.org> <4E55F33C.50203@kernel.org> <4E58731A.7010708@garzik.org> <4E58AE9E.1090601@garzik.org> <4E59478C.9000504@garzik.org> <4E5A129F.1090801@garzik.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mail-qy0-f174.google.com ([209.85.216.174]:49926 "EHLO mail-qy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753654Ab1H2POm (ORCPT ); Mon, 29 Aug 2011 11:14:42 -0400 Received: by qyk15 with SMTP id 15so1013868qyk.19 for ; Mon, 29 Aug 2011 08:14:41 -0700 (PDT) In-Reply-To: Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Pekka Enberg Cc: Linus Torvalds , Sparse Mailing-list On 08/29/2011 10:42 AM, Pekka Enberg wrote: > On Sun, 28 Aug 2011, Jeff Garzik wrote: >> * it will soon be necessary to pay more attention to target-specific >> details. we need some mechanism for specifying i386, x86-64, etc. so >> that we may fill in bits_in_pointer and similar values properly. This >> may involve some sparse hacking IIRC, because sparse (used to be?) >> largely hardcoded to use i386 target values when checking. Or maybe >> this is already done, and I just am ignorant of that area of the code. > > > Can you think of anything else except target.c that needs to be fixed in > sparse? struct layout is what immediately comes to mind. But it is mainly a "only time will tell" answer, most likely. Jeff