From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pekka Enberg Subject: Re: [PATCH] Re: LLVM and PSEUDO_REG/PSEUDO_PHI Date: Mon, 29 Aug 2011 17:45:00 +0300 (EEST) Message-ID: References: <4E5495C9.6050207@kernel.org> <4E55F33C.50203@kernel.org> <4E58731A.7010708@garzik.org> <4E58AE9E.1090601@garzik.org> <4E59478C.9000504@garzik.org> <4E5A129F.1090801@garzik.org> <4E5A15F9.2090007@garzik.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Return-path: Received: from mail-bw0-f46.google.com ([209.85.214.46]:32954 "EHLO mail-bw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753710Ab1H2OpE (ORCPT ); Mon, 29 Aug 2011 10:45:04 -0400 Received: by bke11 with SMTP id 11so4215334bke.19 for ; Mon, 29 Aug 2011 07:45:03 -0700 (PDT) In-Reply-To: <4E5A15F9.2090007@garzik.org> Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Jeff Garzik Cc: Linus Torvalds , Sparse Mailing-list On Sun, 28 Aug 2011, Jeff Garzik wrote: >> Random thoughts / backend status: > > And, > > * a "make check" that exercises our known-working backend tests all the way > through compilation, linking and execution would be VERY helpful. i.e. pass > values to the binops tests, and make sure we receive expected results. > > In the early stages, this may mean linking with a gcc-compiled test harness? Yes, makes sense. We could have a separate test-runner.c that's compiled by GCC. I'm not quite sure how to hook that up into validation/test-runner.c cleanly, though. Pekka