Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Zhao Zhili <quinkblack-at-foxmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] build: fix windows build issue introduced by 45bea45
Date: Fri, 16 May 2025 01:42:02 +0800
Message-ID: <tencent_833EEF56499D62E0105A56343B800234E709@qq.com> (raw)
In-Reply-To: <20250515124603.42691-1-nuomi2021@gmail.com>



> On May 15, 2025, at 20:46, Nuo Mi <nuomi2021@gmail.com> wrote:
> 
> We defined CR to 2 in libavcodec/vvc/dec.h, but the CR used by _IMAGE_ARM64_RUNTIME_FUNCTION_ENTRY winnt.h
> reorder the header will avoid the issue.

There are similar issues of using short uppercase variable names or macro, e.g.,

f0f596dbc6b45b544d2d2d4fb78c0a2bdc3e6eb1

And

b1240c983f96271990c4262978a08edc8eb4df1f

How about limit the scope or add prefix to the macro?

> ---
> tests/checkasm/vvc_sao.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/tests/checkasm/vvc_sao.c b/tests/checkasm/vvc_sao.c
> index 9e6507b2c3..4ad40684fa 100644
> --- a/tests/checkasm/vvc_sao.c
> +++ b/tests/checkasm/vvc_sao.c
> @@ -20,14 +20,13 @@
> 
> #include <string.h>
> 
> +#include "checkasm.h"
> #include "libavutil/intreadwrite.h"
> #include "libavutil/mem_internal.h"
> 
> #include "libavcodec/vvc/dsp.h"
> #include "libavcodec/vvc/ctu.h"
> 
> -#include "checkasm.h"
> -
> static const uint32_t pixel_mask[3] = { 0xffffffff, 0x03ff03ff, 0x0fff0fff };
> static const uint32_t sao_size[] = {8, 16, 32, 48, 64, 80, 96, 112, 128};
> 
> -- 
> 2.34.1
> 
> _______________________________________________
> 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".

_______________________________________________
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".

  reply	other threads:[~2025-05-15 17:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-15 12:46 Nuo Mi
2025-05-15 17:42 ` Zhao Zhili [this message]
2025-05-15 20:31 ` softworkz .
2025-05-16 12:53   ` Nuo Mi

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=tencent_833EEF56499D62E0105A56343B800234E709@qq.com \
    --to=quinkblack-at-foxmail.com@ffmpeg.org \
    --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