vk: Fix memory initialization order in RCB/RDB path

This commit is contained in:
kd-11 2023-09-22 13:32:28 +03:00 committed by kd-11
parent cb21fefbd9
commit 061c10ea69

View File

@ -713,8 +713,8 @@ namespace vk
const auto max_content_size = tiled_region.tile->pitch * utils::align<u32>(subres.height_in_block, 64); const auto max_content_size = tiled_region.tile->pitch * utils::align<u32>(subres.height_in_block, 64);
const auto section_length = std::min(max_content_size, available_tile_size); const auto section_length = std::min(max_content_size, available_tile_size);
vk::load_dma(range.start, section_length);
const auto dma_mapping = vk::map_dma(range.start, section_length); const auto dma_mapping = vk::map_dma(range.start, section_length);
vk::load_dma(range.start, section_length);
const auto scratch_buf = vk::get_scratch_buffer(cmd, section_length * 3); // 0 = linear data, 1 = padding (deswz), 2 = tiled data const auto scratch_buf = vk::get_scratch_buffer(cmd, section_length * 3); // 0 = linear data, 1 = padding (deswz), 2 = tiled data
const auto tiled_data_scratch_offset = section_length * 2; const auto tiled_data_scratch_offset = section_length * 2;
const auto linear_data_scratch_offset = 0; const auto linear_data_scratch_offset = 0;