From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/3] tools/target_dec_fuzzer: set some avctx->export_side_data flags
Date: Tue, 26 Jul 2022 09:16:03 -0300
Message-ID: <bfae256f-a268-9cfe-94ff-df5057bd635f@gmail.com> (raw)
In-Reply-To: <20220719134423.449-1-jamrial@gmail.com>
On 7/19/2022 10:44 AM, James Almer wrote:
> Signed-off-by: James Almer <jamrial@gmail.com>
> ---
> tools/target_dec_fuzzer.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/tools/target_dec_fuzzer.c b/tools/target_dec_fuzzer.c
> index 1587045e02..7d71dd39e3 100644
> --- a/tools/target_dec_fuzzer.c
> +++ b/tools/target_dec_fuzzer.c
> @@ -336,7 +336,7 @@ int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
> if ((flags & 0x10) && c->p.id != AV_CODEC_ID_H264)
> ctx->flags2 |= AV_CODEC_FLAG2_FAST;
> if (flags & 0x80)
> - ctx->flags2 |= AV_CODEC_FLAG2_EXPORT_MVS;
> + ctx->export_side_data |= AV_CODEC_EXPORT_DATA_MVS;
>
> if (flags & 0x40)
> av_force_cpu_flags(0);
> @@ -404,6 +404,8 @@ int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
> ctx->debug |= FF_DEBUG_QP;
> if (flags64 &4)
> ctx->debug |= FF_DEBUG_MB_TYPE;
> + if (flags64 & 8)
> + ctx->export_side_data |= AV_CODEC_EXPORT_DATA_VIDEO_ENC_PARAMS;
>
> if (extradata_size < size) {
> ctx->extradata = av_mallocz(extradata_size + AV_INPUT_BUFFER_PADDING_SIZE);
Will apply the patchset.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2022-07-26 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 13:44 James Almer
2022-07-19 13:44 ` [FFmpeg-devel] [PATCH 2/3] tools/target_dec_fuzzer: set AV_EF_CRCCHECK in avctx->err_recognition James Almer
2022-07-19 13:44 ` [FFmpeg-devel] [PATCH 3/3] tools/target_dec_fuzzer: set avctx->workaround_bugs flags James Almer
2022-07-26 12:16 ` James Almer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bfae256f-a268-9cfe-94ff-df5057bd635f@gmail.com \
--to=jamrial@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git