From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luc Van Oostenryck Subject: Re: Sparse-LLVM issue compiling NULL pointers Date: Fri, 3 Mar 2017 05:21:22 +0100 Message-ID: References: <20170302052124.fsqogvysufayy4to@macbook.local> <20170302135655.s742zcslis5r56if@macpro.local> <20170302160403.zz5efgh34jvjh5q5@macpro.local> <20170302174959.kh7x5bmwccl7fpig@macpro.local> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from mail-qk0-f169.google.com ([209.85.220.169]:34767 "EHLO mail-qk0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751340AbdCCISO (ORCPT ); Fri, 3 Mar 2017 03:18:14 -0500 Received: by mail-qk0-f169.google.com with SMTP id s186so163784956qkb.1 for ; Fri, 03 Mar 2017 00:17:43 -0800 (PST) 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 2, 2017 at 7:02 PM, Dibyendu Majumdar wrote: >> In fact LLVMBuildStore() return a LLVMValueRef. >> Could this be the 'void' we seen? >> > > It returns a Value that is a store instruction, or at least that's the > way I interpret this and so yes, I think the type of this was void. I failed to find doc about it. But anwyay, overwritting the target->priv can't be correct. > BTW removing the line makes progress, but it fails at the add > instruction later. Are there other issues like this you can spot? I am > a bit lost here I am afraid. No, not like this. What I saw was just the result of looking at your example and trying to understand what's happening. Luc