llvm dev - Dec 2020 - Testing the compiler

First, a tangential question: I swear it was the case that when I made a change
to TableGen and then built lib/Target/all, Ninja would rebuild all the target
.inc files. Today it does not. Am I losing my mind?

Anyway, my primary question: What is the best way to test the compiler after
making a change that affects it? In particular, I am changing things in the
xxxGenInstrInfo.inc files. Up until now, I have not had to test the compiler.

I know that that are various executables that run unit tests. Is there something
that ties them all together?

You can run "ninja check-llvm" to run all the tests that belong to
llvm/.
 Similarly "ninja check-clang" tests clang/. "ninja
check-lld" will test
lld. etc.  "ninja check-all" will test all projects enabled with
-DLLVM_ENABLE_PROJECTS from when you ran cmake.

~Craig


On Mon, Dec 14, 2020 at 1:02 PM Paul C. Anagnostopoulos via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> First, a tangential question: I swear it was the case that when I made a
> change to TableGen and then built lib/Target/all, Ninja would rebuild all
> the target .inc files. Today it does not. Am I losing my mind?
>
> Anyway, my primary question: What is the best way to test the compiler
> after making a change that affects it? In particular, I am changing things
> in the xxxGenInstrInfo.inc files. Up until now, I have not had to test the
> compiler.
>
> I know that that are various executables that run unit tests. Is there
> something that ties them all together?
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20201214/7e11ccbb/attachment.html>