Re: [FFmpeg-devel] [PATCH 3/3] avcodec/vulkan_decode: Un-sparse extensions table

Lynne: > Mar 3, 2024, 12:35 by andreas.rheinha...@outlook.com: > >> Only three of the 226 (== AV_CODEC_ID_AV1) entries >> have been used. Unsparsing this table is especially >> important given that this array lives in .data.rel.ro. >> >> Signed-off-by: Andreas Rheinhardt >> --- >> Instead of para

Re: [FFmpeg-devel] [PATCH 3/3] avcodec/vulkan_decode: Un-sparse extensions table

Lynne: > Mar 3, 2024, 12:35 by andreas.rheinha...@outlook.com: > >> Only three of the 226 (== AV_CODEC_ID_AV1) entries >> have been used. Unsparsing this table is especially >> important given that this array lives in .data.rel.ro. >> >> Signed-off-by: Andreas Rheinhardt >> --- >> Instead of para

Re: [FFmpeg-devel] [PATCH 3/3] avcodec/vulkan_decode: Un-sparse extensions table

Mar 3, 2024, 12:35 by andreas.rheinha...@outlook.com: > Only three of the 226 (== AV_CODEC_ID_AV1) entries > have been used. Unsparsing this table is especially > important given that this array lives in .data.rel.ro. > > Signed-off-by: Andreas Rheinhardt > --- > Instead of parallel tables, one c

[FFmpeg-devel] [PATCH 3/3] avcodec/vulkan_decode: Un-sparse extensions table

Only three of the 226 (== AV_CODEC_ID_AV1) entries have been used. Unsparsing this table is especially important given that this array lives in .data.rel.ro. Signed-off-by: Andreas Rheinhardt --- Instead of parallel tables, one could also merge VkCodecMap and VkExtensionProperties (i.e. putting o