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 10:58:00 +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-f53.google.com ([209.85.214.53]:35914 "EHLO mail-it0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752115AbdCAK7v (ORCPT ); Wed, 1 Mar 2017 05:59:51 -0500 Received: by mail-it0-f53.google.com with SMTP id h10so94465518ith.1 for ; Wed, 01 Mar 2017 02:58:01 -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 Hi Luc, 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. Thanks and Regards Dibyendu