From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luc Van Oostenryck Subject: Re: sparse-llvm test cases Date: Fri, 11 Aug 2017 00:50:06 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from mail-oi0-f52.google.com ([209.85.218.52]:35042 "EHLO mail-oi0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752135AbdHJWuH (ORCPT ); Thu, 10 Aug 2017 18:50:07 -0400 Received: by mail-oi0-f52.google.com with SMTP id e124so20180904oig.2 for ; Thu, 10 Aug 2017 15:50:07 -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 On Thu, Aug 10, 2017 at 10:44 PM, Dibyendu Majumdar wrote: > > Yes, the current arrangement is a stop gap. As I develop both on > Windows and Linux, I need a portable solution so I cannot really use > shell scripts. People use bash with mingwin, for example. Would it be something usable for you? >> Another question is that, I don't know how many your test get impact >> by the llvm versions. If it get tight to a specific version of llvm, the >> test case has less value. People will get false positives due to different >> llvm version. If it begin to be the case we'll need to add a new tag telling to ignore the test if version this or that. > The tests are all designed to be runnable I think this is very very important. Of course, you're interested in LLVM output but not only. One thing I want to have for testing linearized code is a simulator for sparse's IR. It's even something quite easy (or at least straightforward) to do. At least once you can associate to each phi-node's 'argument' the parent BB they come from. This is something I'm planning to do for several reasons. -- Luc