From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luc Van Oostenryck Subject: Re: Infinite loop with OOM while testing Sparse on Wine code Date: Fri, 21 Jul 2017 00:44:53 +0200 Message-ID: <20170720224451.goobbxuteej7aksd@ltop.local> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-wr0-f170.google.com ([209.85.128.170]:34220 "EHLO mail-wr0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935477AbdGTWo4 (ORCPT ); Thu, 20 Jul 2017 18:44:56 -0400 Received: by mail-wr0-f170.google.com with SMTP id 12so76131206wrb.1 for ; Thu, 20 Jul 2017 15:44:56 -0700 (PDT) Content-Disposition: inline In-Reply-To: Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Christopher Li Cc: Michael Stefaniuc , Sparse Mailing-list On Wed, Jul 19, 2017 at 02:16:54PM -0700, Christopher Li wrote: > On Wed, Jul 19, 2017 at 4:43 PM, Luc Van Oostenryck > wrote: > > > > I'm not yet fully back but I'll be able to look at it later, probably > > tomorrow (it's already evening here). > > That is fine. How about we temporary disable that in the 0.5.1 release. > Re-enable it with some proper fix of the phi domination problem. e.g. > 0.5.2. > > Right now I feel a little bit uncomfortable with 11b1a83b. Already two bugs > trigger in the field. The previous fix d7985338 is not a proper fix any way. > I think the right thing to do is just release 0.5.1 with 11b1a83b disabled. > Turn on 11b1a83b in sparse-next and do more fixing there. Release > 0.5.2 when it settle down with other new merges. I can't run all the validation I had done for -rc4 but I have no objections about the revert (I'm pretty sure there will be some side-effects though). -- Luc