From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dibyendu Majumdar Subject: Re: Sparse-LLVM issue compiling NULL pointers Date: Thu, 2 Mar 2017 18:02:10 +0000 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-it0-f41.google.com ([209.85.214.41]:34994 "EHLO mail-it0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751148AbdCCCVg (ORCPT ); Thu, 2 Mar 2017 21:21:36 -0500 Received: by mail-it0-f41.google.com with SMTP id 203so5192954ith.0 for ; Thu, 02 Mar 2017 18:21:35 -0800 (PST) In-Reply-To: Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Luc Van Oostenryck Cc: Linux-Sparse On 2 March 2017 at 17:57, Luc Van Oostenryck wrote: >> Removing the last line of output_op_store() (insn->target->priv = target;) >> should fix this. > > 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. 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. Regards