[llvm-dev] Separate test harness for LLVM test-suite

[Roman Lebedev via llvm-dev]

On Mon, Jul 9, 2018 at 10:26 AM, Elena Lepilkina via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Dear community,
>
>
>
> LLVM test-suite includes both default applications (benchmarks, tests) and
> test harness (CMake modules, lit-support, some scripts, etc.). Test suite
> provides extension interface to add “external” tests suite and folders. This
> worked well, we enhanced basic harness and integrated large set of internal
> benchmarks and applications.
>
>
>
> However, we have users interested in LLVM test harness to build, profile,
> test applications and experiment with tools/compilers without using
> applications from full LLVM test-suite (~2,5 Gb).
>
>
>
> Are there reasons why separation of test-suite into 1) basic test-harness
> and 2) applications is undesirable or impossible?
I would like to cautiously +1 this question.

I've been personally eyeing using LNT for personal benchmarking needs,
but so far did not get to it. There seems to be no good docs (with examples!)
on how to actually write an external lnt test producer, which is understandable,
and the test-suite itself is rather tightly coupled with the LLVM.

Thus i too think that such a split into the supporting framework,
and all the actual benchmarks *may* be a good thing.
Or at least i would love to see some good docs.

> We will be glad to hear opinions of community.
>
>
>
> Best regards,
>
> Elena Lepilkina,
Roman.

> Synopsys Corp, ARC processors
>
>
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>