From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Li Subject: Re: [PATCH v3 00/21] improve constexpr handling Date: Fri, 31 Mar 2017 18:40:26 +0800 Message-ID: References: <20161123040528.GA74337@macpro.local> <87a8cqlhcy.fsf@gmail.com> <87polm5eqq.fsf@gmail.com> <87lgwa59nm.fsf@gmail.com> <87h96x5hzv.fsf@gmail.com> <20170329144233.7hjyhshb72pbtv7s@macpro.local> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from mail-it0-f46.google.com ([209.85.214.46]:36175 "EHLO mail-it0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932619AbdCaKk2 (ORCPT ); Fri, 31 Mar 2017 06:40:28 -0400 Received: by mail-it0-f46.google.com with SMTP id e75so10282497itd.1 for ; Fri, 31 Mar 2017 03:40:27 -0700 (PDT) In-Reply-To: Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Luc Van Oostenryck Cc: Nicolai Stange , Linux-Sparse , Josh Triplett On Fri, Mar 31, 2017 at 4:55 PM, Luc Van Oostenryck wrote: > The very first patch of the series insure that all flags are > initialized to the default 'NONE'. Then the next patches build > on this and add info/bits to flags case by case. > > As far as I can see the patch was correct. How about a different test case. The right hand side is a const expression but not an int const expression. So the result is not an address constant. The result should be some other kind of constant since both left hand side and right hand side are both constant expression. If the result has NONE then it is wrong. Chris