| commit | 288cd3bf5fb4269dbcdd7e8ce621f9c8e586693d | |
| author | Artem Zhmurov <zhmurov@gmail.com> | |
| Thu, 17 Sep 2020 12:49:10 +0000 (17 12:49 +0000) | ||
| committer | Paul Bauer <paul.bauer.q@gmail.com> | |
| Thu, 17 Sep 2020 12:49:10 +0000 (17 12:49 +0000) | ||
| tree | d802b043d8a996bc6f6441a4f33b78e5e7511936 | treesnapshot (tar.gz zip) |
| parent | efbbf88ed696d657fbef00045692b20b6a2e693e | commitdiff |
Remove the CPU hardware context from the general list of test hardware contexts
Having CPU code path in the general hardware context list leads to having
many if (CPU) clauses. This complicates things in places, where there are
several CPU runners. Since in most cases (i.e. everywhere apart from Ewald
tests) the runners know the hardware they should use, the selection of CPU
or GPU is now done when the runners are created. TestHardwareContext is
to become TestDeviceContext and will only hold GPU devices.
Having CPU code path in the general hardware context list leads to having
many if (CPU) clauses. This complicates things in places, where there are
several CPU runners. Since in most cases (i.e. everywhere apart from Ewald
tests) the runners know the hardware they should use, the selection of CPU
or GPU is now done when the runners are created. TestHardwareContext is
to become TestDeviceContext and will only hold GPU devices.