From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luc Van Oostenryck Subject: Re: [PATCH 11/29] add PSEUDO_UNDEF Date: Thu, 17 Aug 2017 21:01:02 +0200 Message-ID: References: <20170816153455.97693-1-luc.vanoostenryck@gmail.com> <20170816153455.97693-12-luc.vanoostenryck@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from mail-oi0-f46.google.com ([209.85.218.46]:33125 "EHLO mail-oi0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752236AbdHQTBD (ORCPT ); Thu, 17 Aug 2017 15:01:03 -0400 Received: by mail-oi0-f46.google.com with SMTP id f11so75894565oic.0 for ; Thu, 17 Aug 2017 12:01:03 -0700 (PDT) In-Reply-To: Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Dibyendu Majumdar Cc: Christopher Li , Linux-Sparse , Linus Torvalds On Thu, Aug 17, 2017 at 6:55 PM, Dibyendu Majumdar wrote: >>> Processing in the middle-end are much easier if undefined values >>> have been clearly identified. Once done, we can then make >>> choices like: >>> - always initialize them to zero >>> - allow arbitraly simplification, >> >> Can pick arbitrate initialized value, but can't do arbitraly simplification. >> > > I agree with that. Perhaps a specific default value can be set? I was speaking loosely to say that a lot of simplifications are possible once the involved pseudo(s) is/are undefined. -- Luc