From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 3/6] apv_decode: Improve reporting of decode errors
Date: Sat, 3 May 2025 19:49:34 -0300
Message-ID: <b0c88736-129e-4e23-83e2-7f87d83bec1f@gmail.com> (raw)
In-Reply-To: <20250503175527.1517092-3-sw@jkqxz.net>
[-- Attachment #1.1.1: Type: text/plain, Size: 377 bytes --]
On 5/3/2025 2:55 PM, Mark Thompson wrote:
> +fail:
> + av_log(avctx, AV_LOG_VERBOSE,
> + "Decode error in tile %d component %d.\n",
> + tile_index, comp_index);
> + atomic_fetch_add(&apv->tile_errors, 1);
atomic_fetch_add_explicit(&apv->tile_errors, 1, memory_order_relaxed);
You don't care about order, just atomicity of the operation.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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".
next prev parent reply other threads:[~2025-05-03 22:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-03 17:55 [FFmpeg-devel] [PATCH 1/6] cbs_apv: Always restore tracing state on split fragment error Mark Thompson
2025-05-03 17:55 ` [FFmpeg-devel] [PATCH 2/6] apv_decode: Fix memory leak on decode error Mark Thompson
2025-05-03 22:46 ` James Almer
2025-05-05 16:34 ` Mark Thompson
2025-05-03 17:55 ` [FFmpeg-devel] [PATCH 3/6] apv_decode: Improve reporting of decode errors Mark Thompson
2025-05-03 22:49 ` James Almer [this message]
2025-05-03 17:55 ` [FFmpeg-devel] [PATCH 4/6] cbs_apv: Better constrain tile_width/height_in_mbs Mark Thompson
2025-05-03 17:55 ` [FFmpeg-devel] [PATCH 5/6] apv_entropy: Improve robustness to bitstream errors Mark Thompson
2025-05-03 17:55 ` [FFmpeg-devel] [PATCH 6/6] cbs_apv: Check tile component sizes Mark Thompson
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=b0c88736-129e-4e23-83e2-7f87d83bec1f@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