From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luc Van Oostenryck Subject: Re: Sparse-LLVM issue compiling NULL pointers Date: Thu, 2 Mar 2017 17:10:38 +0100 Message-ID: <20170302161037.yflovl6cdk6y3fqe@macpro.local> References: <20170228150956.moyfiyd5zf7tbeze@macbook.local> <20170302052124.fsqogvysufayy4to@macbook.local> <20170302135655.s742zcslis5r56if@macpro.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-wm0-f53.google.com ([74.125.82.53]:36898 "EHLO mail-wm0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753218AbdCBQSN (ORCPT ); Thu, 2 Mar 2017 11:18:13 -0500 Received: by mail-wm0-f53.google.com with SMTP id n11so29631422wma.0 for ; Thu, 02 Mar 2017 08:17:02 -0800 (PST) Content-Disposition: inline In-Reply-To: Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Dibyendu Majumdar Cc: Linux-Sparse On Thu, Mar 02, 2017 at 02:05:34PM +0000, Dibyendu Majumdar wrote: > On 2 March 2017 at 13:56, Luc Van Oostenryck > wrote: > > On Thu, Mar 02, 2017 at 05:41:59AM +0000, Dibyendu Majumdar wrote: > >> But I am beginning to think that there is quite a bit of work needed > >> to fix the issues, and in any case it might be better to create an > >> LLVM backend from the parse tree rather than the linearized version. > > > > Possible, but this will certainly need some work too. > > > > True, which is why I was hoping that I could at least get the current > version working. Unfortunately even the simplest programs I through at > it fail. Looks like it hasn't really been tested as there is no > defined subset of C that works. > > Maybe if we keep fixing the issues one by one we will get to a point > where it works. I have no doubts about it. Luc