This reverts commit b33ac93c.

Now that logging is done independently from NDEBUG, we can re-enable
"undef NDEBUG for test executables". The rationale that we want to
undefine NDEBUG for test executable is that we want, even in release
builds, asserts in tests enabled. Note that this also applies to
asserts in the emper core library, if those are in *headers*.

use DIE* macros instead of the die function

See merge request i4/manycore/emper!33

make logging configurable during compilation and runtime

See merge request i4/manycore/emper!32

    Compile-time:
      * A new meson option 'log_level' is introduced which has all the values from the
        Loglevel enum
      * The 'OFF' option defines EMPER_LOG_OFF which causes the LOG* macros to be empty
        and the Logger<>::log function to return immediately
      * The default 'automatic' option sets 'log_level' to 'Error' for release builds
        and to 'ALL' otherwise

    Runtime:
      * The global variable emper::log_level defined in Debug.hpp controls the logging output
      * It is initialized with the meson option 'log_level' but can be changed during runtime

make the userspace-rcu dependency optional

See merge request i4/manycore/emper!28

Disable the userpace-rcu support by default.
Our used userspace-rcu flavor memb is rather new and not available in
liburcu version 0.10 available in debian buster.
This change switches from using DCE and "if constexpr" to the C
preprocessor so the library is only needed when the userspace-rcu support
is actually enabled.

[gitlab-ci] Use flowdalic/debian-testing-dev:1.0 as container image

See merge request i4/manycore/emper!34

And fix the #include issues reported by the newer IWYU version.

[UnboundedBlockingMpscQueue] Fix message loss

See merge request i4/manycore/emper!31

Avoid messages getting lost in the queue.

use proper camel case for URCU test

See merge request i4/manycore/emper!26

do not run tests in parallel by default

See merge request i4/manycore/emper!27

[docs] rename doc target from speedymalloc to emper

See merge request i4/manycore/emper!29

Remove -UNDEBUG from tests

See merge request i4/manycore/emper!25

The explicit -UNDEBUG was introduced in the CMake to meson migration (62900cd1)
but as far as I can tell it was not present in the CMake tests definition.

It makes tests less reliable because it enables only some debug messages but not
all.
For example if emper is build with NDEBUG a test using a Semaphore
will output debug messages from the Semaphore but not from the Runtime.

[test] add AlarmActorTest

See merge request i4/manycore/emper!24

register each worker thread for userspace RCU using the default flavor

See merge request i4/manycore/emper!23

Introduce a new Actor test using BinaryPrivateSemaphores and an Actor.
Multiple fibers are created which create a BPS on the stack, submit it to the actor
and wait on the semaphore.
The Actor simply signals each semaphore it receives.

The SimpleURCUTest creates a lock-less hash table and inserts values from
separate fibers and verifies the correct insertion.

The default flavor is the preferred way to use the userspace library it uses
the sys_membarrier syscall or falls back to using userspace membarriers.

This adds the liburcu dependency which must be installed regardless the
'liburcu' meson option.

Tests

See merge request i4/manycore/emper!22

[test] Use test_name as test name, not the description

See merge request i4/manycore/emper!21

This allows to run indiviual tests using the meson runner, e.g.

meson --repeat 100 SimpleActorTest

[Makefile] The 'check' target should also run the smoke tests

See merge request i4/manycore/emper!20

Re-enable SimpleActorTest

See merge request i4/manycore/emper!19

The IWYU version in the CI wants to remove this include, my locally
installed IWYU wants to keep this.

Florian Fischer authored 4 years ago and Florian Schmaus committed 4 years ago

Concurrently using the CLOG_CONFIG map can result in a segmentation fault.

To prevent concurrent access to LOG_CONFIG a new constexpr getLevelFor
is introduces analogue to getTagFor.

This should not change much, but ensure that this method is also
invoked in the test (even though it is not explicitly tested).

Otherwise meson will use a random value.