瀏覽代碼

Add version of existing suppression for the case when the compiler doesn't optimize the tail call

Samuel Thibault 10 年之前
父節點
當前提交
30f5601d92
共有 1 個文件被更改,包括 21 次插入0 次删除
  1. 21 0
      tools/valgrind/starpu.suppr

+ 21 - 0
tools/valgrind/starpu.suppr

@@ -81,11 +81,32 @@
 }
 
 {
+   TODO1: This is temporary. It perhaps does not pose problem because only the worker takes this mutex. Fixing this will require changing the scheduler interface, so that the schedulers themselves take the scheduling lock, not the caller. Filter it out for now, so we can see other races more easily.
+   Helgrind:LockOrder
+   fun:pthread_mutex_lock
+   fun:starpu_pthread_mutex_lock
+   fun:_starpu_sched_component_worker_lock_scheduling
+   fun:simple_worker_pull_task
+   ...
+}
+
+{
+   TODO2: This is temporary. It perhaps does not pose problem because only the worker takes this mutex. Fixing this will require changing the scheduler interface, so that the schedulers themselves take the scheduling lock, not the caller. Filter it out for now, so we can see other races more easily.
+   Helgrind:LockOrder
+   fun:pthread_mutex_lock
+   fun:starpu_pthread_mutex_lock
+   fun:_starpu_sched_component_lock_worker
+   fun:simple_worker_pull_task
+   ...
+}
+
+{
    TODO2: This is temporary. It perhaps does not pose problem because only the worker takes this mutex. Fixing this will require changing the scheduler interface, so that the schedulers themselves take the scheduling lock, not the caller. Filter it out for now, so we can see other races more easily.
    Helgrind:LockOrder
    fun:pthread_mutex_lock
    fun:starpu_pthread_mutex_lock
    fun:_starpu_sched_component_lock_worker
+   fun:_starpu_sched_component_worker_lock_scheduling
    fun:simple_worker_pull_task
    ...
 }