From 6a159a09bec9d2c739b12f7b36f01323d6f2ba68 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Storsj=C3=B6?= Date: Thu, 19 Dec 2024 14:43:04 +0200 Subject: [PATCH] [docs] Mention ffmpeg and dav1d in llvm-test-suite Since https://github.com/llvm/llvm-test-suite/pull/182 and https://github.com/llvm/llvm-test-suite/pull/188, these projects can now be added as external projects within llvm-test-suite. --- llvm/docs/TestSuiteGuide.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/llvm/docs/TestSuiteGuide.md b/llvm/docs/TestSuiteGuide.md index 35984bd6f7b3b..aa8332ed8b7e1 100644 --- a/llvm/docs/TestSuiteGuide.md +++ b/llvm/docs/TestSuiteGuide.md @@ -367,6 +367,19 @@ For the SPEC benchmarks you can switch between the `test`, `train` and `ref` input datasets via the `TEST_SUITE_RUN_TYPE` configuration option. The `train` dataset is used by default. +In addition to SPEC, the multimedia frameworks ffmpeg and dav1d can also +be hooked up as external projects in the same way. By including them in +llvm-test-suite, a lot more of potentially vectorizable code gets compiled +- which can catch compiler bugs merely by triggering code generation asserts. +Including them also adds small code correctness tests, that compare the +output of the compiler generated functions against handwritten assembly +functions. (On x86, building the assembly requires having the nasm tool +available.) The integration into llvm-test-suite doesn't run the projects' +full testsuites though. The projects also contain microbenchmarks for +measuring the performance of some functions. See the `README.md` files in +the respective `ffmpeg` and `dav1d` directories under +`llvm-test-suite/External` for further details. + Custom Suites -------------