las3_pub / predictable_parallel_patterns

This avoids issues with doubling the measurement vector sizes influencing memory measures.

Currently once we are serial no more parallel strains are executed. However, this could be changed using strain local resources in the future.

The strain_local resources can be used to get unique IDs for resources that would, in a serial execution, only be used once in the call chain. This is a first prototype implementation and needs further tesitng. The current implementation adds linear overhead to each steal proportional to the number of used  resources. We might be able to reduce it, but for a first version it is fine.

The flag can be used to run code annotated with PLS outside of a scheduler environment,
i.e. the app does not crash if the code is called without context. The compile option
allows to omit all spawn and sync calls during compilation, creating the equivalent serial code.

Basic profiling works. Next steps are to 'refine' the interface, i.e. allow to disable parts of the profiling and better output for some stats. Maybe look at storing/loading the DAG's with stats to/from disk.

Add key-points required to capture an execution DAG. Currently all data is in-memory and printed out. In future work it would be good to store the DAG's and/or process them further.

Remove easy profiler for now. It might be useful for later on to get a grasp of general behaviour, but because of its issues with coroutines it is not worth profiling code with it right now.

Merge continuation-style into master branch

See merge request !13

Our benchmarks require isolation from other system effects. Additionally,
we would like to have a system with 'very symmetric cores' (no hyperthreading,
no different memory connections, ....) that falls more into  the embedded
class of devices than desktop processors do. The notes describe how to setup
an banana pi m3 with a linux distri with rt preemt patch to achieve this.

Tsan needs the fix for not leaking fibers on the server to work properly.
Disable the tests until we can somehow easily get a build of it on the CI server.

I am not sure if this is appropriate, but it works and is no focus of this project.

Make sure that the guard page leads to sigsegv as expected.

It is now possible to use a memory mapped stack that throws a SIGSEV if thes coroutine stacks are exhausted.