From: "Martin Storsjö" <martin@martin.st>
To: "Swinney, Jonathan" <jswinney@amazon.com>
Cc: "Pop, Sebastian" <spop@amazon.com>,
"ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 1/2] checkasm: added additional dstW tests for hscale
Date: Wed, 25 May 2022 11:25:29 +0300 (EEST)
Message-ID: <58ba7bc-d8c1-b240-c5dc-e6177f16f1f@martin.st> (raw)
In-Reply-To: <36fdb39238cf499c815f9c2704381656@EX13D07UWB004.ant.amazon.com>
On Wed, 25 May 2022, Swinney, Jonathan wrote:
> Signed-off-by: Jonathan Swinney <jswinney@amazon.com>
> ---
> tests/checkasm/sw_scale.c | 38 ++++++++++++++++++++++----------------
> 1 file changed, 22 insertions(+), 16 deletions(-)
>
> diff --git a/tests/checkasm/sw_scale.c b/tests/checkasm/sw_scale.c
> index 3c0a083b42..6c223c48f9 100644
> --- a/tests/checkasm/sw_scale.c
> +++ b/tests/checkasm/sw_scale.c
> @@ -148,7 +148,11 @@ static void check_hscale(void)
> { 8, 18 },
> };
>
> - int i, j, fsi, hpi, width;
> +#define LARGEST_INPUT_SIZE 512
> +#define INPUT_SIZES 6
> + static const int input_sizes[INPUT_SIZES] = {8, 24, 128, 144, 256, 512};
> +
While these are all nice even values, would it make sense to test things
with uneven sizes too?
This patch does seem good to me, however it does break the checkasm test
on x86. Offhand I don't know where it differs between how swscale is used
in reality (where I presume it does work just fine) and how it's set up in
checkasm.
// 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:[~2022-05-25 8:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 1:21 Swinney, Jonathan
2022-05-25 8:25 ` 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=58ba7bc-d8c1-b240-c5dc-e6177f16f1f@martin.st \
--to=martin@martin.st \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=jswinney@amazon.com \
--cc=spop@amazon.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