avcodec: Add padding after the remaining AVFrames
This limits ABI issues in case libavcodec is linked to a libavutil with larger AVFrame Which can happen if they are shiped in seperate binary packages and libavutil is upgraded A cleaner alternative would be to replace them by pointers but this would likely cause a small speedloss Signed-off-by: Michael Niedermayer <michaelni@gmx.at> (cherry picked from commit fc567ac49e17151f00f31b59030cd10f952612ef) Conflicts: libavcodec/h264.h (cherry picked from commit 618d062bd553a7d7fad194d4236913f2b0a0251e) Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
This commit is contained in:
parent
e39a992bd1
commit
0c88d539f8
@ -99,6 +99,7 @@ struct MpegEncContext;
|
|||||||
*/
|
*/
|
||||||
typedef struct Picture{
|
typedef struct Picture{
|
||||||
struct AVFrame f;
|
struct AVFrame f;
|
||||||
|
uint8_t avframe_padding[1024]; // hack to allow linking to a avutil with larger AVFrame
|
||||||
ThreadFrame tf;
|
ThreadFrame tf;
|
||||||
|
|
||||||
AVBufferRef *qscale_table_buf;
|
AVBufferRef *qscale_table_buf;
|
||||||
|
@ -807,6 +807,7 @@ int avcodec_default_get_buffer(AVCodecContext *avctx, AVFrame *frame)
|
|||||||
typedef struct CompatReleaseBufPriv {
|
typedef struct CompatReleaseBufPriv {
|
||||||
AVCodecContext avctx;
|
AVCodecContext avctx;
|
||||||
AVFrame frame;
|
AVFrame frame;
|
||||||
|
uint8_t avframe_padding[1024]; // hack to allow linking to a avutil with larger AVFrame
|
||||||
} CompatReleaseBufPriv;
|
} CompatReleaseBufPriv;
|
||||||
|
|
||||||
static void compat_free_buffer(void *opaque, uint8_t *data)
|
static void compat_free_buffer(void *opaque, uint8_t *data)
|
||||||
|
Loading…
x
Reference in New Issue
Block a user