From: Wu Jianhua <toqsxw@outlook.com> To: Nuo Mi <nuomi2021@gmail.com>, FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: [FFmpeg-devel] 回复: [PATCH] avcodec/x86/vvc/vvcdsp_init: fix linking error when configuring with --disable-ssse3 --disable-optimizations options Date: Mon, 15 Apr 2024 17:47:37 +0000 Message-ID: <OSZP286MB2173A3DC5D3EB7CE296F2679CA092@OSZP286MB2173.JPNP286.PROD.OUTLOOK.COM> (raw) In-Reply-To: <CAFXK13e6eo=+KhFf2hXdTs=DiLQXjRLpc3r6i8DTyx2U0832mA@mail.gmail.com> > 发件人: Nuo Mi <nuomi2021@gmail.com> > 发送时间: 2024年3月3日 6:49 > 收件人: FFmpeg development discussions and patches > 抄送: Wu Jianhua > 主题: Re: [FFmpeg-devel] [PATCH] avcodec/x86/vvc/vvcdsp_init: fix linking error when configuring with --disable-> > ssse3 --disable-optimizations options > > Thank you, Jianhua. > This patch mixes many things. > Could you help split it into smaller, more atomic patches? > For example, one for moving code blocks and another for fixing --disable-ssse3. > Sure. I sent the v2. > #define AVG_INIT(bd, opt) do { \ > - c->inter.avg = bf(avg, bd, opt); \ > - c->inter.w_avg = bf(w_avg, bd, opt); \ > + c->inter.avg = bf(ff_vvc_avg, bd, opt); \ > + c->inter.w_avg = bf(ff_vvc_w_avg, bd, opt); \ > Why change the function scope to fix a compilation issue? I use the same way that adds prototypes for the functions as HEVC DSP. Hence, the functions cannot be declared with static and need the prefix to avoid naming conflict. _______________________________________________ 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:[~2024-04-15 17:47 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-29 17:41 [FFmpeg-devel] " toqsxw 2024-03-03 14:49 ` Nuo Mi 2024-04-15 17:47 ` Wu Jianhua [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=OSZP286MB2173A3DC5D3EB7CE296F2679CA092@OSZP286MB2173.JPNP286.PROD.OUTLOOK.COM \ --to=toqsxw@outlook.com \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=nuomi2021@gmail.com \ /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