From: "Martin Storsjö" <martin@martin.st> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: xufuji456 <839789740@qq.com> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/aarch64/hevc: add transform_luma_4x4_neon note: run_count=1000, CPU=Cortex A53 transform_4x4_luma_neon: 45 transform_4x4_luma_c: 103 Date: Wed, 22 Mar 2023 10:06:27 +0200 (EET) Message-ID: <fad4aa4-1554-53f3-d044-d0ddf9fc5d7f@martin.st> (raw) In-Reply-To: <tencent_1B05DC303B246F683954C8209B3946807105@qq.com> On Sat, 11 Mar 2023, xufuji456 wrote: > --- > libavcodec/aarch64/hevcdsp_idct_neon.S | 52 ++++++++++++++++++++++- > libavcodec/aarch64/hevcdsp_init_aarch64.c | 2 + > 2 files changed, 53 insertions(+), 1 deletion(-) Overall the code seems fine, but there's a couple more minor issues: - There's no checkasm test, so we don't have any continuous tracking that this function doesn't break ABI details subtly. From reading the code it seems fine, but we really want to have checkasm coverage for all new assembly. Can you please add one? It should hopefully not be very complicated given the existing tests for other idct parts. - The commit message is a bit garbled - not all that text belongs in the subject line. - It was hard to get the patch applied: > diff --git a/libavcodec/aarch64/hevcdsp_idct_neon.S b/libavcodec/aarch64/hevcdsp_idct_neon.S > index b11f56862a..00d9690466 100644 > --- a/libavcodec/aarch64/hevcdsp_idct_neon.S > +++ b/libavcodec/aarch64/hevcdsp_idct_neon.S > @@ -665,4 +667,52 @@ idct_dc 16, 8 > idct_dc 16, 10 > > idct_dc 32, 8 > -idct_dc 32, 10 > \ No newline at end of file > +idct_dc 32, 10 The file upstream actually did have the proper newline at the end of the file (some earlier patch of yours, I think, were missing this but I fixed it up when pushing it), but the patch expected a file without a trailing newline. It would be much less hassle for me to apply the patch if it was properly rebased on the actually pushed git master version. // Martin _______________________________________________ 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:[~2023-03-22 8:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-11 3:18 xufuji456 2023-03-22 8:06 ` Martin Storsjö [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=fad4aa4-1554-53f3-d044-d0ddf9fc5d7f@martin.st \ --to=martin@martin.st \ --cc=839789740@qq.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