Skip to content
Snippets Groups Projects
Select Git revision
  • master default
  • ci-bump-test
  • abp-queue
  • new-delete-leaks
  • fused-continuation-and-completion-stealing
  • emper-fix-invalid-conv
  • remote-put-get-free-context-cycle
  • linux-version-construct-on-first-use
  • libstdc++-asserts
  • msan
  • libc++
  • completer-strategies
  • cactus_stack_devel_one_commit
  • client-load-change
  • cppcheck
  • flow
  • cast-if-future
  • async_network2
  • thread_safe_log_config
  • burak
  • attic/clang-release-tls-optimization-debug-and-fix
  • attic/continuation-stealing-dev
22 results

emper

  • Clone with SSH
  • Clone with HTTPS
    • Forked from Lehrstuhl für Informatik 4 (Systemsoftware) / manycore / emper
    Source project has a limited visibility.
    user avatar
    [CallerEnvironment] Add a new OWNER caller environment
    Florian Fischer authored 
    The OWNER caller environment can be used when the executed algorithm
should be different if the current worker owns the objects it touches.
For example a worker reaping completions on a foreign IoContext may
use the EMPER callerEnvironment and the worker of the IoContext OWNER.

Also implement the stream operator to print caller environments.
    69e73b98
    History
    user avatar 69e73b98
    History
    Name Last commit Last update