aboutsummaryrefslogtreecommitdiffstats
path: root/tests/checkasm/checkasm.c
diff options
context:
space:
mode:
authorMartin Storsjö <martin@martin.st>2023-12-16 00:33:59 +0200
committerMartin Storsjö <martin@martin.st>2023-12-21 00:14:41 +0200
commitf5e3e9e04e83820e093f789a2f77c5f3b48797b2 (patch)
tree2bbf7c4e9c06cffd325510bfd5c4694639647e4f /tests/checkasm/checkasm.c
parent89215237dd6ac64f94e14aa20a000e0440a00aac (diff)
downloadffmpeg-f5e3e9e04e83820e093f789a2f77c5f3b48797b2.tar.gz
checkasm: Remove unnecessary const on scalar parameters
The ffmpeg coding style doesn't usually use const on scalar parameters (or on the pointer values - as opposed to the type that is pointed to, where it has a semantic meaning), contrary to the dav1d coding style (where this was imported from). This avoids warnings about differences in the type signatures between declaration and definition of this function, with older versions of MSVC. The issue was observed with one version of MSVC 2017, 19.16.27024.1, with warnings like these: src/tests/checkasm/checkasm.c(969): warning C4028: formal parameter 3 different from declaration The warning itself is bogus as the const here is harmless, and newer versions of MSVC no longer warn about this. Signed-off-by: Martin Storsjö <martin@martin.st>
Diffstat (limited to 'tests/checkasm/checkasm.c')
-rw-r--r--tests/checkasm/checkasm.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/tests/checkasm/checkasm.c b/tests/checkasm/checkasm.c
index 6318d9296b..daa5438f88 100644
--- a/tests/checkasm/checkasm.c
+++ b/tests/checkasm/checkasm.c
@@ -933,10 +933,10 @@ void checkasm_report(const char *name, ...)
}
#define DEF_CHECKASM_CHECK_FUNC(type, fmt) \
-int checkasm_check_##type(const char *const file, const int line, \
+int checkasm_check_##type(const char *file, int line, \
const type *buf1, ptrdiff_t stride1, \
const type *buf2, ptrdiff_t stride2, \
- const int w, int h, const char *const name) \
+ int w, int h, const char *name) \
{ \
int y = 0; \
stride1 /= sizeof(*buf1); \