Thanks to Nicolas Pfeiffer for writing the initial prototypical
implementation of continuation stealing and the cactus stack
mechanism, on which this is based.

Co-authored-by: Nicolas Pfeiffer <pfeiffer@cs.fau.de>

The meson generated clang-tidy target uses compile_commands including
all code from subprojects and therefore fails due to code not in our control.
The gitlab CI also uses the tidy make target.

The ninja 'iwyu' target does not depend nor generates
compile_commands_wo_subprojects/compile_commands.json. Hence iwyu
would fail if the database is not yet generated or run with an
outdated compile_commands.json.

Instead of iwyu being added to STATIC_ANALYSIS_NINJA_TARGETS, we now
have the static-analysis make target depend on iwyu. This ensures that
compile_commands_wo_subprojects/compile_commands.json is generated or
updated (if required) before iwyu is run.p

Generate a new compile_commands database in compile_commands_wo_subprojects/
without the files in subprojects/.
This new compile_commands database is than consumed by iwyu and clang-tidy.

Co-Authored-By: Florian Schmaus <schmaus@cs.fau.de>
Suggested--By: Florian Schmaus <schmaus@cs.fau.de>

This should improve the CI response time, as we now (potentially)
perform iwyu and clang-tidy in parallel.

This adds yet another target "smoke-test-suite", which just runs all
tests in the 'smoke' test suite. The static-analysis target was
changed to include *all* static analysis thingies we have, even 'doc'
as Doxygen does also do some checks that the documentation is
"correct".

The smoke-test target is also kept, as it allows developers to simply
run all smoke tests. Furthermore, this adds some missing PHONY
declarations in the Makefile.

The gitlab-ci now runs the smoke-test-suite and static-analysis
targets in two different jobs. Previously the smoke-test would also
run the static-analysis target, which was not intended.

The 'static-analysis' Make target runs all static analysis we
currently have. This allows to run at least static analysis, in cases
where we are able build a particular EMPER configuration, but no able
to execute it (e.g. because the kernel lacks io_uring support).

Fixes #8.

Also move setup.sh from scripts/ to tools/.

and not Make

to allow for e.g. "make VERBOSE=1"