From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dibyendu Majumdar Subject: Re: Sparse-LLVM issue compiling NULL pointers Date: Wed, 1 Mar 2017 14:45:03 +0000 Message-ID: References: <20170228150956.moyfiyd5zf7tbeze@macbook.local> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from mail-it0-f45.google.com ([209.85.214.45]:35438 "EHLO mail-it0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751035AbdCAOpg (ORCPT ); Wed, 1 Mar 2017 09:45:36 -0500 Received: by mail-it0-f45.google.com with SMTP id 203so99304237ith.0 for ; Wed, 01 Mar 2017 06:45:04 -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 1 March 2017 at 10:58, Dibyendu Majumdar wrote: > On 28 February 2017 at 17:03, Luc Van Oostenryck > wrote: >> On Tue, Feb 28, 2017 at 4:09 PM, Luc Van Oostenryck >> wrote: >>> There is indeed some problems regarding this, we looked a bit at this >>> some weeks ago. However I firmly believe that the information about >>> the type belong to the operations and not the values. >> > > I am trying to work out how a value pseudo correct type can be > determined when the pseudo is a function call argument. Would > appreciate any pointers on this. The current implementation of > pseudo_to_value() uses the function call instruction which is > incorrect. > I have implemented a solution that get the type information from the function prototype for pseudo values when processing function arguments, but not sure this is correct. Anyway have hit a bunch of other issues with sparse-llvm ... :-( Regards Dibyendu