Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Lynne <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PR] ffv1_vulkan: use an internal CRC table (PR #21515)
Date: Mon, 19 Jan 2026 12:06:03 -0000
Message-ID: <176882436414.25.8937552115373193290@4457048688e7> (raw)

PR #21515 opened by Lynne
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21515
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21515.patch

Since the recent CRC changes, get_table returns arch-dependent tables.


>From 5f7ab229191440e3f1737afbb32ef9380d880790 Mon Sep 17 00:00:00 2001
From: Lynne <dev@lynne.ee>
Date: Mon, 19 Jan 2026 13:04:24 +0100
Subject: [PATCH] ffv1_vulkan: use an internal CRC table

Since the recent CRC changes, get_table returns arch-dependent tables.
---
 libavcodec/ffv1_vulkan.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libavcodec/ffv1_vulkan.c b/libavcodec/ffv1_vulkan.c
index 6f49e2ebb1..d8fa963491 100644
--- a/libavcodec/ffv1_vulkan.c
+++ b/libavcodec/ffv1_vulkan.c
@@ -114,7 +114,7 @@ int ff_ffv1_vk_init_crc_table_data(FFVulkanContext *s,
                          VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT));
     RET(ff_vk_map_buffer(s, vkb, (void *)&buf_mapped, 0));
 
-    memcpy(buf_mapped, av_crc_get_table(AV_CRC_32_IEEE), buf_len);
+    memcpy(buf_mapped, crctab, buf_len);
 
     RET(ff_vk_unmap_buffer(s, vkb, 1));
 
-- 
2.52.0

_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

                 reply	other threads:[~2026-01-19 12:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=176882436414.25.8937552115373193290@4457048688e7 \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=code@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