From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: sparse-llvm test cases
Date: Thu, 10 Aug 2017 21:44:19 +0100 [thread overview]
Message-ID: <CACXZuxdvBVV+gDzWmFs=FA_s5Ric1djbF7mLNiea06SaSiqUOQ@mail.gmail.com> (raw)
In-Reply-To: <CANeU7Q=zF9hRqnNCN-+p0Y64yfkyaBvroeSP7faM4DSWW2RW5g@mail.gmail.com>
Hi Chris,
On 10 August 2017 at 19:38, Christopher Li <sparse@chrisli.org> wrote:
> On Sun, Mar 12, 2017 at 9:13 PM, Dibyendu Majumdar
> <mobile@majumdar.org.uk> wrote:
>> https://github.com/dibyendumajumdar/dmr_c/tree/master/tests
>>
> I take a brief look. I think it has way to many duplicate copy of the
> testrun.sh. You might want to think coherently what exactly is need
> for your different test case. It is better to have one frame work to
> support all the test case.
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.
>
> 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.
>
The tests are all designed to be runnable - i.e. you can generate the
code and run it either with lli or by generating an executable - so
they are completely independent of LLVM version. But they do need all
the LLVM fixes that are still pending as without those fixes most
tests won't even compile. Nevertheless we can start incorporating
these tests gradually so that when the LLVM fixes are all in then we
will have a good set of tests.
I would prefer to add validation of the Sparse IR as well - at present
I record these but do not try to validate mainly as I think Sparse IR
output is still changing so we need to get to a stable point first.
Regards
Dibyendu
next prev parent reply other threads:[~2017-08-10 20:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 1:13 sparse-llvm test cases Dibyendu Majumdar
2017-08-10 18:01 ` Christopher Li
2017-08-10 22:41 ` Luc Van Oostenryck
2017-08-10 18:38 ` Christopher Li
2017-08-10 20:44 ` Dibyendu Majumdar [this message]
2017-08-10 20:59 ` Christopher Li
2017-08-12 13:46 ` Dibyendu Majumdar
2017-08-12 13:59 ` Christopher Li
2017-08-10 22:50 ` Luc Van Oostenryck
2017-08-10 23:55 ` Christopher Li
2017-08-12 13:44 ` Dibyendu Majumdar
2017-08-12 14:43 ` Luc Van Oostenryck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACXZuxdvBVV+gDzWmFs=FA_s5Ric1djbF7mLNiea06SaSiqUOQ@mail.gmail.com' \
--to=mobile@majumdar.org.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).