From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dibyendu Majumdar Subject: Re: Sparse 0.5.1 RC5 released. Date: Mon, 14 Aug 2017 00:20:13 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from mail-ua0-f182.google.com ([209.85.217.182]:38588 "EHLO mail-ua0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751202AbdHMXUO (ORCPT ); Sun, 13 Aug 2017 19:20:14 -0400 Received: by mail-ua0-f182.google.com with SMTP id w45so31175645uac.5 for ; Sun, 13 Aug 2017 16:20:14 -0700 (PDT) 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 14 August 2017 at 00:17, Dibyendu Majumdar wrote: > On 14 August 2017 at 00:10, Luc Van Oostenryck > wrote: >> On Mon, Aug 14, 2017 at 12:55 AM, Dibyendu Majumdar >> wrote: >>> Here it is: >>> >>> https://github.com/dibyendumajumdar/dmr_c/blob/mergesparse/tests/minilua/minilua_preprocessed.c >> >> OK, thanks. >> >> I see here: >> 1) 4 errors with a bitcast wich different sizes on each side. >> I'm a bit surprised as the code seems to do the right thing when >> emitting a bitcast, I'll need to check >> 3) 3 errors of pointer compare with different types. >> It should be easy to fix. >> > > When you say you are seeing errors ... do you mean by running > sparse-llvm? That won't necessarily match what I get. > I mean to say that I am interested in fixing the Sparse IR generation - so if these are errors in the IR you spotted, then great (I am amazed at how quickly you found the errors!). Regards Dibyendu