| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
range sizes.
Fixes infinite loop in find_grid_optimal_factor() in cases where the
user specifies a grid size with less dimensions than the device
supports.
Reported-by: Tom Stellard <[email protected]>
Cc: "10.0" <[email protected]>
(cherry picked from commit 99d447cc5dafa3a36b970068961989cced62e3b6)
|
|
|
|
|
|
|
|
| |
Inspired by a patch sent to the mailing list by Tom Stellard, but
using a different algorithm to calculate the optimal block size that
has been found to be considerably more effective.
Reviewed-by: Tom Stellard <[email protected]>
|
|
|
|
|
| |
Variadic template aliases make these versions of GCC very confused,
write down the full type spec instead.
|
|
|
|
|
|
|
|
| |
kernel object.
Based on a similar fix from Aaron Watry. It seems unlikely that we
will ever need a kernel-specific setting for this, and the Gallium API
doesn't support it. Remove kernel::max_block_size() altogether.
|
|
Tested-by: Tom Stellard <[email protected]>
|