You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently trying to run the C++ benchmarks FilterBank and NQueens several times after each other on an odroid ux4 platform while also limiting the execution to either all big or all little cores with taskset --cpu-list. Within these repetitions it seems to almost always come to a deadlock.
The exact command I am running is:
taskset --cpu-list 0-3 ./FilterBank
Unfortunatly, compiling with the --logging debug option seems to resolve the issue, so that I can not provide more information on when exactly the deadlocks occur.
The text was updated successfully, but these errors were encountered:
Thanks for reporting! This is likely an issue with thu usage of atomic variables in reactor-cpp, which is more challenging to get right on ARM architectures.
I am currently trying to run the C++ benchmarks FilterBank and NQueens several times after each other on an odroid ux4 platform while also limiting the execution to either all big or all little cores with taskset --cpu-list. Within these repetitions it seems to almost always come to a deadlock.
The exact command I am running is:
taskset --cpu-list 0-3 ./FilterBank
Unfortunatly, compiling with the --logging debug option seems to resolve the issue, so that I can not provide more information on when exactly the deadlocks occur.
The text was updated successfully, but these errors were encountered: