gdb/amdgpu: Silence wave termination messages
authorLaurent Morichetti <laurent.morichetti@amd.com>
Thu, 7 Sep 2023 18:00:53 +0000 (11:00 -0700)
committerLancelot Six <lancelot.six@amd.com>
Fri, 15 Sep 2023 16:12:30 +0000 (16:12 +0000)
After commit 9d7d58e7262, the amdgpu target started printing
"thread exited" messages when pruning waves that had terminated.

  ...
  [AMDGPU Wave ?:?:?:2045 (?,?,?)/? exited]
  [AMDGPU Wave ?:?:?:2046 (?,?,?)/? exited]
  [AMDGPU Wave ?:?:?:2047 (?,?,?)/? exited]
  [AMDGPU Wave ?:?:?:2048 (?,?,?)/? exited]
  ...

The issue was that before commit 9d7d58e7262, delete_thread was silent
by default due to a bug that the commit fixed.

Replaced the amdgpu target call to delete_thread with a call to
delete_thread_silent.

Change-Id: Ie5d5a4c5be851f092d2315b2afa6a36a30a05245
Approved-By: Simon Marchi <simon.marchi@efficios.com>
gdb/amd-dbgapi-target.c

index 22c269b7992c95c127871ad11a72f0f5e2ad2970..8eafceac5696b53ca7b1d7be3c7062d6bed2ab6b 100644 (file)
@@ -1634,7 +1634,7 @@ amd_dbgapi_target::update_thread_list ()
            auto it = threads.find (tp->ptid.tid ());
 
            if (it == threads.end ())
-             delete_thread (tp);
+             delete_thread_silent (tp);
            else
              threads.erase (it);
          }